To get a backtrace do a "make debug" and then cause the crash. On your system core dumps aren't just called "core", but core.xxx where xxx is the procees number. So after the crash, look for the latest core.xxx and do a
gdb ./obj_linux_x86_d/gnugk core.xxx bt and thats the backtrace we are looking for. It should show us what GnuGk did when it crashed. Regards, Jan Shamun wrote: > Hello Jan, > > Here is the complete build process, but still same ex: > http://fpaste.org/iKfP/ > > Thanks & Reg > Shamun -- Jan Willamowius, j...@willamowius.de, http://www.gnugk.org/ ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________________ Posting: mailto:Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
