Do you notice an infinite loop (increased CPU usage)? If that is the
case, you could interrupt several times, obtain a backtrace and
continue.
Tip: to limit to the last five frames use "bt 5" instead of "bt". For
more info about a command, use "help bt".
Note that if the program hangs or aborts a
Thanks a lot of the explaination :-)
Here is the backtrace. I don't think Qt is involved.
(gdb) bt
#0 dissect_ieee802154_payload_mlme_sub_ie (offset=8, tree=0x7f078bbd4690,
pinfo=0x11b81c8, tvb=0x1000f70) at packet-ieee802154.c:2628
#1 dissect_ieee802154_payload_ie (offset=8, tree=,
pinfo=0x11b8
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, 2
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-
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
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 1
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 2
