Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 9834] segfault in »tshark -G values«

Date: Wed, 05 Mar 2014 03:41:02 +0000

changed bug 9834

What Removed Added
Status IN_PROGRESS INCOMPLETE

Comment # 2 on bug 9834 from
(In reply to comment #1)
> (In reply to comment #0)
> > Build Information:
> > TShark 1.10.5 (SVN Rev Unknown from unknown)
> > 
> > Unfortunately I cannot easily build newer versions from git's master-1.10
> > branch due to Arch using Python 3 as /usr/bin/python, and the .py scripts
> > included in Wireshark's build process simply don't run with Python 3
> > (TabErrors and similar issues).
> > 
> 

I've backported fixes for 2 python scripts to git/master-1.10. Wireshark
git/master-1.10 now builds AOK for me with python3.




> > I have confirmed, though, that the bug does not appear with tshark built
> > from git's master branch.
> 

I've backported to git/master-1.10 two fixes to packet-selfm.c to fix 2
messages:
"Warning: Extended value string ... forced to fall back to linear search".

However, I've not been able to duplicate the segfault you've reported on my
Fedora 32-bit system. Something which shows up on 64 bits ?

Can you do a build with the current git/master-1.10 and see what happens when
you do 'tshark -G values' ?

Thanks


You are receiving this mail because:
  • You are watching all bug changes.