https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6690
--- Comment #7 from Jim Young <jyoung@xxxxxxx> 2012-06-22 16:02:11 PDT ---
Created attachment 8660
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8660
console output with bv-debug.patch applied
Yes this is running on a MAC. Virtually 100% of the time I launch Wireshark
from a bash shell.
I first started "script" to capture Wireshark's console output.
I then launched the locally built wireshark with the command "./wireshark &".
I added visual breaks between the various steps used to replicate the extra
space issue with bash prompts by pressing on the "return" key while focus was
in the bash shell.
I also annotated the shell output with comment (#) records describing what
action I was about to do or had just completed within the Wireshark GUI.
Hope this console report helps.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
