Hello, first enable coredumps # ulimit -c unlimited # ./yourfaultyapp
open another shell and kill the process using kill -SIGSEGV then it should say core dumped (also compile your application with -g .. there are a few other debugging options but that one might already help you) afterwards run your application with gdb (should look like the following line) # gdb ./yourfaultyapp coredumpfile > bt // for a backtrace, last functions which got called and so > frame #<framenumber> // inspect a frame > list // show the sourcecode which is connected to that frame hope this helps, Markus On 8/16/05, r_zaca <[EMAIL PROTECTED]> wrote: > Hello all, > > I have a program that just stops execution and I can't see what is really > going on. Does anyone know how this kind of problem shoud be solved. I've > already read something about core dump memory, but I don't know how to make > it, or instruct my program to do that. Can anyone help me? > > p.s.) My program runs on a Linux machine. > > Thanks. > > -- Markus Rechberger http://www.wikiservice.at/dse/wiki.cgi?MarkusRechberger - To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
