On 2009-12-12, at 11:25 , Charles Lepple wrote: > On Sat, Dec 12, 2009 at 6:58 AM, Kevin Horton <khorto...@rogers.com> wrote: >> Thread 0 Crashed: >> 0 libSystem.B.dylib 0x9574ae42 __kill + 10 >> 1 libSystem.B.dylib 0x957bd23a raise + 26 >> 2 libSystem.B.dylib 0x957c9679 abort + 73 >> 3 libglib-2.0.0.dylib 0x00e976d0 g_logv + 1074 >> 4 libglib-2.0.0.dylib 0x00e9777d g_log + 41 >> 5 libglibmm-2.4.1.dylib 0x00af346a >> Glib::exception_handlers_invoke() + 302 >> 6 libglibmm-2.4.1.dylib 0x00af434f >> Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) > > It looks like the call into libsystem happened when libglib called > abort() on line 2, which would tend to shift the blame away from OS X. > > The traceback after line 6 probably won't be much help without a > complete stack dump, since it looks like the main GTK+/GLib event > loop.
Thanks for your comments. The only part of the crashdump log that I didn't send is the rather long list of binary images. Would that be useful? Assuming this is a repeatable event for this user, is there a way to capture a complete stack dump. "dpkg -S libglib-2.0.0.dylib" reports that libglib-2.0.0.dylib comes from glib2-shlibs. No one else has reported a crashing problem, so it is possible that something is amiss in the user's Fink installation. Would a "fink rebuild glib2-shlibs" be in order? -- Kevin Horton Ottawa, Canada ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
