Wireshark-bugs: [Wireshark-bugs] [Bug 10079] Buildbot crash output: fuzz-2014-05-06-21601.pcap
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 06 May 2014 18:11:15 +0000

changed bug 10079

What Removed Added
Status CONFIRMED RESOLVED
Resolution --- WORKSFORME

Comment # 3 on bug 10079 from 
(In reply to comment #2)
> I downloaded & ran this trace in tshark without a problem. I was unable to
> repeat the error.

Alright then, if it shows up again I'll dig deeper but for now I'm calling this
a fluke.

> This is my first time reading a builder report. The problem is thsark
> returning 139, correct? Since there is no debug trace, am I correct in
> assuming that the program didn't crash, it just returned non-zero?

139 is the standard linux exit code for a SIGSEGV, meaning either a
null-pointer dereference or an access to invalid memory or the like. It was a
crash.

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