Control: fixed -1 2.0.0~rc2+g74e5b56-1
On Thu, 4 Jun 2015 23:19:02 +0200 =?UTF-8?B?QsOhbGludCBSw6ljemV5?=
wrote:
...
> 2015-06-02 13:54 GMT+02:00 Joao S Veiga :
...
> > Please let me know if you need any more information or tests.
> Thank you, this seems to be enough to fix the issue.
And the fi
Control: forwarded -1 https://code.wireshark.org/review/#/c/8765/
Control: tags -1 upstream
Hi Joao,
2015-06-02 13:54 GMT+02:00 Joao S Veiga :
>> Please install wireshark-dbg and run "ulimit -c unlimited" before
>> reproducing the issue. This will generate a core file which you can
>> analyze wit
Please install wireshark-dbg and run "ulimit -c unlimited" before
reproducing the issue. This will generate a core file which you can
analyze with gdb.
Please attach the stack trace to see what is crashing.
I ran a quick test on my computer and tshark ran fine.
Cheers,
Balint
Thank you Balint,
Hi Joao,
2015-06-01 20:42 GMT+02:00 Joao S Veiga :
> Package: tshark
> Version: 1.12.1+g01b65bf-4
> Severity: minor
>
> tshark consistently shows "Segmentation fault" when exiting from a capture or
> capture attempt (tshark -G does not do it, but normal user without cap
> permissions does it). A
Package: tshark
Version: 1.12.1+g01b65bf-4
Severity: minor
tshark consistently shows "Segmentation fault" when exiting from a capture or
capture attempt (tshark -G does not do it, but normal user without cap
permissions does it). Apart from this, it seems to work ok.
### exiting spontaneously:
5 matches
Mail list logo
