On 2009-12-12, at 17:46 , Daniel Johnson wrote:

> 
> On Dec 12, 2009, at 4:18 PM, Kevin Horton wrote:
> 
>> 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?  
> 
> A more detailed reading would be that during Glib::Source::dispatch_vfunc() 
> in glibmm2.4, something Bad happened which raised an exception 
> (Glib::exception_handlers_invoke()). The exception handler printed an error 
> message (g_log()) and killed the program with abort(). So the actual problem 
> was in glibmm2.4. There should have been an error message printed to stderr 
> and/or Console.app by g_log(). That message might be helpful.


I asked the user to rebuild glibmm2.4-shlibs, and to report any messages in 
terminal or Console.app.  He reported back:

> I rebuilt glibmm2.4-shlibs but now the gtk frontend crashes
> completely with the x-window.  Earlier only cadabra kernel was
> crashing.
> 
> I get the following messages on the terminal from where xcadabra
> is launched.
> #############
> (xcadabra:5104): Gtk-WARNING **: Unable to find default local directory 
> monitor type
> 
> (xcadabra:5104): Gtk-WARNING **: Unable to find default local directory 
> monitor type
> 
> (xcadabra:5104): Gtk-WARNING **: Unable to find default local directory 
> monitor type
> 
> (xcadabra:5104): Gtk-WARNING **: Unable to find default local directory 
> monitor type
> ##############
> 
> I am also attaching the crash report with this mail.
> 
> Following is the Console.app entry just before the crash.
> ##############
> Sun Dec 13  22:23 27 10:23:27 PM org.x.startx[4476] AllocNewConnection: 
> client index = 5, socket fd = 18
> ##############
> I think console.app does not have useful information regarding this problem.  
> However,
> my assessment may be wrong.

The crashlog he sent starts with:

Process:         xcadabra [5112]
Path:            /sw/bin/xcadabra
Identifier:      xcadabra
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  bash [4451]

Date/Time:       2009-12-13 22:24:03.472 -0500
OS Version:      Mac OS X 10.5.8 (9L31a)
Report Version:  6
Anonymous UUID:  F665AC4C-68D5-43B0-9BF5-F1A278A90B69

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000e9a5cdc0
Crashed Thread:  0

Thread 0 Crashed:
0   libSystem.B.dylib                   0x956e53e5 tiny_malloc_from_free_list + 
235
1   libSystem.B.dylib                   0x956de1cd szone_malloc + 180
2   libSystem.B.dylib                   0x956de0d8 malloc_zone_malloc + 81
3   libSystem.B.dylib                   0x956de06c malloc + 55
4   libgio-2.0.0.dylib                  0x00c19e07 xdg_check_dir + 86
5   libgio-2.0.0.dylib                  0x00c19c54 xdg_run_command_on_dirs + 173
6   libgio-2.0.0.dylib                  0x00c1a0fb xdg_mime_init + 92
7   libgio-2.0.0.dylib                  0x00c1a48c 
_gio_xdg_get_mime_type_for_data + 38
8   libgio-2.0.0.dylib                  0x00be3a93 g_content_type_guess + 370
9   libgdk_pixbuf-2.0.0.dylib           0x00c76483 _gdk_pixbuf_get_module + 48
10  libgdk_pixbuf-2.0.0.dylib           0x00c76932 gdk_pixbuf_new_from_file + 
421
11  libgdkmm-2.4.1.dylib                0x00669842 
Gdk::Pixbuf::create_from_file(std::basic_string<char, std::char_traits<char>, 
std::allocator<char> > const&) + 42
12  xcadabra                            0x0000e77f 
TeXEngine::convert_set(std::set<TeXEngine::TeXRequest*, 
std::less<TeXEngine::TeXRequest*>, std::allocator<TeXEngine::TeXRequest*> >&) + 
4495
13  xcadabra                            0x0001178c TeXEngine::convert_all() + 44
14  xcadabra                            0x00029598 
XCadabra::load(std::basic_string<char, std::char_traits<char>, 
std::allocator<char> > const&, bool) + 568
15  xcadabra                            0x0002b3f8 XCadabra::on_file_open() + 
408
16  libglibmm-2.4.1.dylib               0x00af8575 
Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) + 45
17  libgobject-2.0.0.dylib              0x00e2df10 g_closure_invoke + 348
18  libgobject-2.0.0.dylib              0x00e3c718 signal_emit_unlocked_R + 3526
19  libgobject-2.0.0.dylib              0x00e3d4c9 g_signal_emit_valist + 1839
20  libgobject-2.0.0.dylib              0x00e3d734 g_signal_emit + 41
21  libgtk-x11-2.0.0.dylib              0x006e9284 _gtk_action_emit_activate + 
80
22  libgobject-2.0.0.dylib              0x00e2df10 g_closure_invoke + 348
23  libgobject-2.0.0.dylib              0x00e3bfa3 signal_emit_unlocked_R + 1617
24  libgobject-2.0.0.dylib              0x00e3d4c9 g_signal_emit_valist + 1839
25  libgobject-2.0.0.dylib              0x00e3d734 g_signal_emit + 41
26  libgtk-x11-2.0.0.dylib              0x008a5493 gtk_widget_activate + 121
27  libgtk-x11-2.0.0.dylib              0x007b59dc gtk_menu_shell_activate_item 
+ 302
28  libgtk-x11-2.0.0.dylib              0x007b5b08 
gtk_menu_shell_button_release + 216
29  libgtk-x11-2.0.0.dylib              0x007a46e4 _gtk_marshal_BOOLEAN__BOXED 
+ 175
30  libgobject-2.0.0.dylib              0x00e2df10 g_closure_invoke + 348
31  libgobject-2.0.0.dylib              0x00e3c537 signal_emit_unlocked_R + 3045
32  libgobject-2.0.0.dylib              0x00e3d533 g_signal_emit_valist + 1945
33  libgobject-2.0.0.dylib              0x00e3d734 g_signal_emit + 41
34  libgtk-x11-2.0.0.dylib              0x008a577f gtk_widget_event_internal + 
718
35  libgtk-x11-2.0.0.dylib              0x007a2c28 gtk_propagate_event + 373
36  libgtk-x11-2.0.0.dylib              0x007a3227 gtk_main_do_event + 1212
37  libgdk-x11-2.0.0.dylib              0x00b68330 gdk_event_dispatch + 85
38  libglib-2.0.0.dylib                 0x00e9066f g_main_context_dispatch + 484
39  libglib-2.0.0.dylib                 0x00e91d22 g_main_context_iterate + 1062
40  libglib-2.0.0.dylib                 0x00e91fd7 g_main_loop_run + 605
41  libgtk-x11-2.0.0.dylib              0x007a2466 gtk_main + 172
42  libgtkmm-2.4.1.dylib                0x0037d659 Gtk::Main::run() + 27
43  xcadabra                            0x000490eb main + 2299
44  xcadabra                            0x000029c6 start + 54

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x65706170  ebx: 0x956e5315  ecx: 0x02c11610  edx: 0xe9a5cdc0
  edi: 0x013a0000  esi: 0x02c00000  ebp: 0xbfffba98  esp: 0xbfffba20
   ss: 0x0000001f  efl: 0x00210286  eip: 0x956e53e5   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0xe9a5cdc0

Binary Images:
===================

I'm not sure what to suggest next.  Any advice is appreciated.

--
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

Reply via email to