On 11/29/15 4:35 PM, lj wrote:
> Several people including me have reported on the linuxquestions.org
> Slackware forum that Wireshark-2.0 crashes (segfault) at startup.
>
> The Qt UI version of Wireshark-2.0.0 will crash on startup for us, every
> time. We have different hardware, including both 32 and 64 bit systems. All
> of us are using Slackware Linux, but some have the stable Slackware-14.1,
> and some are using "Slackware Current" which has more up-to-date packages.
> My version of Qt is 4.8.7, but others report the crash with Qt5. The crash
> is immediate, with nothing displayed. Even "wireshark --help" crashes.
>
> Wireshark-1.12.8 works fine on these systems, both Gtk+ and Qt UIs.
>
> Wireshark-2.0.0 with the Gtk+3 UI works also.
>
> Wireshark-2.0.0 with Qt always crashes. Below is a gdb traceback.
>
> Are there any ideas of what we can try?
What does `gcc --version` print? The output below looks similar to the test
case in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19916
but that's a pretty old bug.
> Program received signal SIGSEGV, Segmentation fault.
> QList (l=..., this=0x864f940 <colors_>)
> at /usr/lib/qt/include/QtCore/qlist.h:122
> 122 inline QList(const QList<T> &l) : d(l.d) { d->ref.ref(); if
> (!d->sharable) detach_helper(); }
> (gdb) bt full
> #0 QList (l=..., this=0x864f940 <colors_>)
> at /usr/lib/qt/include/QtCore/qlist.h:122
> No locals.
> #1 __static_initialization_and_destruction_0 (__initialize_p=1,
> __priority=65535) at io_graph_dialog.cpp:82
> No locals.
> #2 _GLOBAL__sub_I_colors_ () at io_graph_dialog.cpp:2319
> No locals.
> #3 0x083a31fd in __do_global_ctors_aux ()
> No symbol table info available.
> #4 0x08073668 in _init ()
> No symbol table info available.
> #5 0x00000000 in ?? ()
> No symbol table info available.
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
