https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4754
--- Comment #6 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-05-14 14:42:02 PDT ---
(In reply to comment #5)
> 2) About gdb I wish I knew how to use it, however I managed to do this (please
> let me know what should I do so that I learn for the future):
> $ sudo libtool --mode=execute gdb wireshark
You shouldn't need to use libtool unless you're running Wireshark from a build
environment (which I don't think you are). Just do:
sudo gdb wireshark
then run Wireshark until it crashes (actually it'll probably look like the GUI
hangs and then you need to switch back to your gdb session where you'll see
that GDB has said something about the process having received a signal or
something).
Once back in gdb, type "bt full" to get the back trace. That'll at least be a
start.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.