Bug 624032 - wireshark segfaults on several pcap files from regression test
Summary: wireshark segfaults on several pcap files from regression test
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: wireshark
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Jan Safranek
QA Contact: Karel Srot
Keywords: Regression
Depends On:
Blocks: 590615 604312
TreeView+ depends on / blocked
Reported: 2010-08-13 13:24 UTC by Karel Srot
Modified: 2010-11-10 21:55 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-11-10 21:55:02 UTC

Attachments (Terms of Use)
wireshark cap/pcap files from the regression test (746.31 KB, application/x-gzip)
2010-08-13 13:24 UTC, Karel Srot
no flags Details

Description Karel Srot 2010-08-13 13:24:25 UTC
Created attachment 438682 [details]
wireshark cap/pcap files from the regression test

Description of problem:
During the regression testing of bugs 604312, 590615 I have found that wireshark/tshark segfaults on several pcap files from a regression test.
This is a regression, previous version wireshark-1.2.9-2.el6 does not segfault.

Unfortunately I am not able to identify what was the origin of those segfaults in the passed and provide related bug/patch. There may be only one unfixed error in wireshark but also there may be several independent errors.

Version-Release number of selected component (if applicable):

How reproducible:
always (tested on x86_64)

Steps to Reproduce:
1. download attached archive
2. tar -xzf tshark_crashers.tar.gz
3. for FILE in crashers/*cap; do tshark -nVr $FILE &> /dev/null || echo $FILE; done;
Actual results:
wireshark/tshark segfaults

Expected results:
no segfaults

Comment 4 Jan Safranek 2010-08-16 10:39:47 UTC
It seems to be already reported (and fixed) upstream:

Comment 5 Jan Safranek 2010-08-16 11:06:22 UTC
..and upstream fix (SVN rev. 33704) seem to fix the crashes.

Comment 11 releng-rhel@redhat.com 2010-11-10 21:55:02 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.