https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4314
beroset@xxxxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |beroset@xxxxxxxxxxxxxx
--- Comment #4 from beroset@xxxxxxxxxxxxxx 2012-10-02 11:53:26 PDT ---
(In reply to comment #3)
> Is this bug still applicable? I tried to reproduce this with a recent
> development version of Wireshark, and I can't. How long does the Info column
> have to be before it gets truncated without having an extra custom column
> following it? In my test case, the entire summary line was 181 chars and the
> text in the Info column was 101 characters. If it requires something longer
> than that, then please post a capture file containing 1 packet with an Info
> column long enough to expose the bug.
I just tried it as well with a line that has a 518 character Info column and
also had no problem (with SVN rev 45122). A quick and easy way to produce a
sample is to point a browser to a real web site but ask for a page with an
absurdly long URL. Wireshark reproduces the GET and the entire page name in
the Info column.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
