> If caught, I will be expelled.
Surely that's only a problem if you've already copied it from someone else?
If yours is original, and can cite first publication, then it's the copiers who are in the frame.
Sometimes, the threats are empty - http://news.bbc.co.uk/1/hi/education/7434277.stm
If you've managed to comment out most of the code with /**/, then just delete all that and post a small example which crashes. That should address your concerns.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Well, you have an extra { on your code posted. But apart from that i compiled it and tested it. It runs fine. Doesn't give me segmentation faults. It is also highly unlikely you ll have one line 100kb, so that shouldn't be the problem. So somewhere else is the problem?
Are you sure you are not getting a segmentation fault. Then it must be the UNIX environment
This is just frustrating.
What is a good debugger, I can use which can use?
Would the debugger also access functions from another code file when called upon?
Well, I m sure. Tested 2-3 files. Do you get seg fault for every file you test? Seeing again the code, I don't think you should get a seg fault.
Try replacing scanf() with the one that takes us parameter the file (I think it is sscanf) . Maybe try initializing code[] to '\0' or something. I can't think of anything else and everything should work ok in the first plase.
Before you do anything, try copying this code in a different file and compiling/running again. Maybe you are missing something between your /* */ (happened many time).
cheers
When I try running the code you gave with a file with more than 100000 characters before a space, I didn't get a segfault, but I got no output either. Make of that what you will.
What is a good debugger, I can use which can use?
Would the debugger also access functions from another code file when called upon?
GDB is a famous one. You use a flag -ggdb when you compile and then you run GDB. Google and find manual. But you need to see how it works, and I don't know how it works with functions from other files etc etc
gdb is too complicated to use when using external files.
Is there any other good debugger?
What do you mean by "too complicated to use when using external files?" gdb is used by many developers all over the world in very complex projects. What are these "external files" of which you speak that are mucking up your life so much?
