On Wed, 19 Nov 2003 10:19:19 +1000 (EST) Mark Livingstone <[EMAIL PROTECTED]> wrote:
ML> RV> > (gdb) exec-file M (gdb) run Starting program: /usr/local/bin/M [New Thread ML> RV> > 16384 (LWP 17694)] ML> RV> > ML> RV> > Program received signal SIGSEGV, Segmentation fault. [Switching to Thread ML> RV> > 16384 (LWP 17694)] 0x00000000 in ?? () ML> RV> ML> RV> Does it happen in debugger only? Does it still happen after complete ML> RV> cleanup? In any case, make sure that you have at least gdb 5.3 and ML> RV> (probably) better 6.0. ML> ML> I am using 5.3-22mdk. Will see if they have a 6.0 version. I did a clean and ML> rebuild and it still happens. It only started after I got Vadim's latest set ML> of Python changes and only happens if you build --with-python. A non-Python ML> build is fine leading me to believe that last batch of diff's must contain the ML> problem. [EMAIL PROTECTED] build]$ /usr/local/bin/gdb GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu". (gdb) exec-file M (gdb) run Starting program: /usr/local/bin/M [New Thread 16384 (LWP 22120)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 22120)] 0x00000000 in ?? () (gdb) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
