https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4314
--- Comment #3 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2012-10-02 11:06:11 PDT ---
(In reply to comment #0)
> When I want to print out the packets information to a file,
> With a long info column, the information can't be fully printed out,
> The information column always stops at a position in the middle of the
> information column,
> But if I add a custom column to the end, the info column can be printed fully,
> it looks strange, can anyone look at this problem?
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.
For reference, my build information:
Version 1.9.0 (SVN Rev 45238 from /trunk)
Compiled (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Sep 24 2012), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, with AirPcap 4.1.1 build 1838.
Built using Microsoft Visual C++ 10.0 build 40219
--
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.
