You can attach to an existing process by its process ID:
gdb -q -p `pidof wireshark`
then once attached, you can can obtain a backtrace with the "bt"
command. You can use "c" to continue and press Ctrl-C in gdb to
interrupt and enter commands like "bt".
Kind regards,
Peter
On Thu, Jun 01, 2017 at 04:33:49PM +0200, Remy Leone wrote:
> I'm not sure to understand. Wireshark doesn't crash but hangs in that case.
> How could I get a symbolized stack trace?
>
> I've tried before to use libtool --mode=execute gdb ./wireshark but
> wireshark keeps hanging and I don't know how to use it to get meaningful
> information.
>
> Best regards
>
> R�my
>
> 2017-06-01 16:24 GMT+02:00 Peter Wu <peter@xxxxxxxxxxxxx>:
>
> > It could be a bug in the Qt GUI component of Wireshark. Is it possible
> > to attach a debugger to "wireshark" or "dumpcap" and obtain a symbolized
> > stack trace?
> >
> > Kind regards,
> > Peter
> >
> > On Tue, May 23, 2017 at 03:51:58PM +0200, Remy Leone wrote:
> > > I'm not sure about where to start investigating this issue. Where does
> > the
> > > critical operation happen when wireshark/tshark is sniffing? I suppose
> > that
> > > this is a problem of blocking read/write that is not happening properly
> > but
> > > I'm not sure about how to get started to investigate this.
> > >
> > > 2017-05-23 10:35 GMT+02:00 Jaap Keuter <jaap.keuter@xxxxxxxxx>:
> > >
> > > > Hi,
> > > >
> > > > You could inspect the bug database, but as far as I know this is not a
> > > > known issue.
> > > > Your setup seems rather normal, so that should not be cause for any
> > > > problems.
> > > > If you could investigate further into tun / named pipe capture
> > behaviour
> > > > that could be interesting.
> > > >
> > > > Thanks,
> > > > Jaap
> > > >
> > > >
> > > > > On 23 May 2017, at 09:27, Remy Leone <remy.leone@xxxxxxxx> wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I've stumbled upon the following problem with master branch of
> > > > Wireshark: After a while (around 10 minutes) Wireshark (master) hangs
> > when
> > > > it's sniffing on a tun interface or a named pipe.
> > > > > On the other side, when I use the last stable version of Wireshark
> > > > (2.2.6) I can sniff on the same interface or named pipe without
> > troubles
> > > > for a long time.
> > > > >
> > > > > Was there any change lately that would have caused that? I got the
> > > > stable version of Wireshark installed through ubuntu repository/ppa. My
> > > > user id also belongs to the wireshark group and I can sniff without
> > root
> > > > priviledges. Could the hanging be caused by that? Is that a classical
> > > > problem?
> > > > >
> > > > > Best regards
> > > > >
> > > > > R�my