Wireshark-bugs: [Wireshark-bugs] [Bug 9952] Buildbot crash output: fuzz-2014-04-02-7762.pcap
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 25 Feb 2015 02:39:43 +0000

Comment # 11 on bug 9952 from 
Created attachment 13473 [details]
The frame that causes the Valgrind errors

(In reply to Peter Wu from comment #10)
> Jeff, can you reproduce it with an empty .wireshark dir? (by setting envvar
> HOME=/x). Can you attach a debugger and print pinfo->fd->num when the
> invalid read occurs?

Yes, I can.

The problem only shows up with Valgrind so the only way to find the offending
packet was to split the capture into pieces until I got down to 1 frame. I
attached that one frame.

What's really amusing is that that frame loads clean in Wireshark (no sign of
an exception) yet Valgrind still complains.

I tried building with ASAN and it doesn't complain either.

It's quite possible it's a Valgrind bug.

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