On Tue, 18 Nov 2003 18:45:41 +0100 (CET) Robert Vazan <[EMAIL PROTECTED]> wrote:
RV> > (gdb) exec-file M (gdb) run Starting program: /usr/local/bin/M [New Thread RV> > 16384 (LWP 17694)] RV> > RV> > Program received signal SIGSEGV, Segmentation fault. [Switching to Thread RV> > 16384 (LWP 17694)] 0x00000000 in ?? () (gdb) RV> > RV> > As you can see, you don't even get started :-( RV> RV> Does it happen in debugger only? Does it still happen after complete RV> cleanup? In any case, make sure that you have at least gdb 5.3 and RV> (probably) better 6.0. I am using 5.3-22mdk. Will see if they have a 6.0 version. I did a clean and rebuild and it still happens. It only started after I got Vadim's latest set of Python changes and only happens if you build --with-python. A non-Python build is fine leading me to believe that last batch of diff's must contain the problem. HTH Dr. QA ------------------------------------------------------- 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
