[Wireshark-bugs] [Bug 14342] Buildbot crash output: randpkt-2018-01-13-5392.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14342

Guy Harris  changed:

   What|Removed |Added

 Resolution|NOTABUG |DUPLICATE

--- Comment #3 from Guy Harris  ---


*** This bug has been marked as a duplicate of bug 14107 ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14342] Buildbot crash output: randpkt-2018-01-13-5392.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14342

Guy Harris  changed:

   What|Removed |Added

  Component|Dissection engine   |Capture file support
   |(libwireshark)  |(libwiretap)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14342] Buildbot crash output: randpkt-2018-01-13-5392.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14342

Guy Harris  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Guy Harris  ---
Yup, this is failing exactly as it should.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14342] Buildbot crash output: randpkt-2018-01-13-5392.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14342

bero...@mindspring.com changed:

   What|Removed |Added

 CC||bero...@mindspring.com

--- Comment #1 from bero...@mindspring.com ---
This doesn't seem to me to be a real problem.  Here are the two data packet
headers:

[2777] offset 0x2d5fdc
ts_sec: 0xad9
ts_usec: 0x0
incl_len: 0xec
orig_len: 0xec

[2778] offset 0x2d60d8
ts_sec: 0x134f4b46
ts_usec: 0x7e69df8b
incl_len: 0x6f513db2
orig_len: 0x3b8e8d4a

Frame 2777 is fine, but Frame 2778 is clearly not right.  Given the header data
provided, it seems to me that what should happen is that exactly what does
happen: pcap detects the error, does NOT allocate an absurd amount of memory
and bails out with an error.  Not sure what else it could do.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe