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 20:20:09 +0000

Comment # 2 on bug 12183 from Jim Young

Verbose debug messages can be enabled by editing the main preferences file
(historically ~/.wireshark/preferences on OS X):

-#console.log.level: 28
+console.log.level: 255

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 12183] tshark with randpktdump reporting "pointer being freed was not allocated" on exit
Next by Date: [Wireshark-bugs] [Bug 12184] New: MATE AVPL match modes "Loose" and "Every" do not work correctly
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