Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12183] tshark with randpktdump reporting "pointer being freed was not allocate

Wireshark-bugs: [Wireshark-bugs] [Bug 12183] tshark with randpktdump reporting "pointer being fr

Date: Fri, 26 Feb 2016 22:40:27 +0000

What	Removed	Added
CC		[email protected]

Comment # 3 on bug 12183 from Michael Mann

Is this two bugs?
1. The fact that randpktdump is run by "default"
2. Use-after-free error potentially caused by randpktdump running.

Potential fix for use-after-free at https://code.wireshark.org/review/14180/
(not sure but it seems to be in the neighborhood)

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 12183] New: tshark with randpktdump reporting "pointer being freed was not allocated" on exit
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 12173] Wireshark use-after-free in wtap_optionblock_free
Next by Date: [Wireshark-bugs] [Bug 12183] tshark with randpktdump reporting "pointer being freed was not allocated" on exit
Previous by thread: [Wireshark-bugs] [Bug 12183] tshark with randpktdump reporting "pointer being freed was not allocated" on exit
Next by thread: [Wireshark-bugs] [Bug 12183] tshark with randpktdump reporting "pointer being freed was not allocated" on exit
Index(es):
- Date
- Thread