Wireshark-dev: Re: [Wireshark-dev] Segmentation fault on startup of wireshark
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Rich Alderson <wireshark@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 20 Jul 2009 17:51:46 -0400 (EDT)
> Date: Sun, 19 Jul 2009 18:19:58 -0600
> From: Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx>

> On Fri, Jul 17, 2009 at 09:28:34PM -0400, Rich Alderson wrote:

>> I have just built the latest stable version of wireshark on Slackware 
>> 12.2, after building all of the prerequisites.

> Try running the GNU Debugger (gdb) and launch Wireshark from it and show 
> us the back trace so we can get an idea of what is going on.  It's 
> pretty simple:

> >gdb wireshark
>  <snip>
> (gdb) run
>  <receive segmentation fault message>
> (gdb) bt 10

    MDE ~> gdb wireshark
    GNU gdb 6.8
    Copyright (C) 2008 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "i486-slackware-linux"...
    (gdb) run --display=:0
    Starting program: /usr/bin/wireshark --display=:0
    [Thread debugging using libthread_db enabled]

    [1]+  Stopped                 gdb wireshark
    MDE ~> fg
    gdb wireshark
    [New Thread 0xb583f6c0 (LWP 9773)]

    Program received signal SIGTTOU, Stopped (tty output).
    [Switching to Thread 0xb583f6c0 (LWP 9773)]
    0xb5b8c29e in __write_nocancel () from /lib/libpthread.so.0
    (gdb) bt 10
    #0  0xb5b8c29e in __write_nocancel () from /lib/libpthread.so.0
    #1  0xb5cf542a in write_string (fd=2,
        string=0x8262250 "\n(wireshark:9773): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed\n")
        at gmessages.c:130
    #2  0xb5cf66b8 in IA__g_log_default_handler (log_domain=0xb5dc6e5b "GLib-GObject", log_level=<value optimized out>,
        message=0x8261fe8 "g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed", unused_data=0x0) at gmessages.c:950
    #3  0xb5cf5877 in IA__g_logv (log_domain=0xb5dc6e5b "GLib-GObject", log_level=G_LOG_LEVEL_CRITICAL,
        format=0xb5d47381 "%s: assertion `%s' failed", args1=0xbfd6a27c "\323\205\334\265iy\334\265Es\324\265\024") at gmessages.c:474
    #4  0xb5cf5a5e in IA__g_log (log_domain=0xb5dc6e5b "GLib-GObject", log_level=G_LOG_LEVEL_CRITICAL,
        format=0xb5d47381 "%s: assertion `%s' failed") at gmessages.c:517
    #5  0xb5cf5c18 in IA__g_return_if_fail_warning (log_domain=0xb5dc6e5b "GLib-GObject",
        pretty_function=0xb5dc85d3 "g_object_get_qdata", expression=0xb5dc7969 "G_IS_OBJECT (object)") at gmessages.c:532
    #6  0xb5da0c0b in IA__g_object_get_qdata (object=0xbfd6a3c4, quark=549) at gobject.c:2450
    #7  0xb5f0c25b in ?? () from /usr/lib/libpangocairo-1.0.so.0
    #8  0xbfd6a3c4 in ?? ()
    #9  0x00000225 in ?? ()
    (More stack frames follow...)
    (gdb) quit
    The program is running.  Exit anyway? (y or n) y
    MDE ~>

Please note the transcribed octal in stack frame #3.  The 8-bit characters kept
driving emacs nuts when I c&p'd from the window in which I was running
wireshark, so I had to paste them into an emacs on that window and transcribe.
It's <capital O-acute>\205<capital U-umlaut><mu>iy<capital U-umlaut><mu>Es<capital O-circumflex><mu>\024
on my screen, in case that's actually important to know.

Thanks for the suggestion.  I see that it's something from pango...

                                                                Rich Alderson