The core dump file can be used to retrieve information about the crash. The most important information is the point when the crash occured - this information is called "stack backtrace". You can get this info (let's say core dump file is named "core.123") using "gdb" program: gdb ./simph323 -core ./core.123 and then entering "bt" command at the gdb prompt. Maybe there is also another (simplier way) to get backtrace info... The important issue is that the backtrace info is useful only if debugger symbols are not stripped from the executable. So the compilation must be performed with "-s" flag disabled and "-g" flag present. Optimizations can be turned on. To strip the symbols from the executable (when these are not required), "strip" command can be used. "P.P." <block111@xxxxxxx> wrote: >> Do you mean that ~/openh323/samples/simple/obj_linux_x86_r/simph323 gets compiled, >> but it cannot be run? Do you get some error message or a core dump? > >I\'ve got core dump a few times. The question is - what should I do with this, >how can I track possible problem using this dump?? (is a textual file)?? ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
