On 28 Jul 2010, at 07:55, Curt, WE7U wrote: > On Thu, 22 Jul 2010, Robert Mead wrote: > >> Using the latest CVS of Xastir, I get a segfault on closing any of >> the station list dialog boxes. I'm running Mac OS X 10.6.4 on a >> multiprocessor machine, which I mention since it seems to be >> related to threading. While doing a GDB step-through of >> list_gui.c:station_list_destroy_shell, it does not crash. >> >> I can't find the offending line, since I think I'm segfaulting >> somewhere in the Xt code after something's been mistakenly free'd >> and my gdb-fu is not strong. > > Any Mac people seeing the same, or can help him debug this? I can confirm it's happening with me as well (10.6.4). I don't normally go in there, so I hadn't spotted it up to now.
Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x000000000000002b 0x0000000100dc643f in SortChildren () (gdb) bt #0 0x0000000100dc643f in SortChildren () #1 0x0000000100fdbb8b in XtPhase2Destroy () #2 0x0000000100fdbd62 in _XtDoPhase2Destroy () #3 0x0000000100fdf46f in XtDispatchEvent () #4 0x0000000100fdf571 in XtAppMainLoop () #5 0x00000001000bdf77 in main (argc=1, argv=0x7fff5fbff8f8, envp=<value temporarily unavailable, due to optimizations>) at ../../xastir/src/main.c:27950 (gdb) _______________________________________________ Xastir-dev mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
