https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3051
Summary: IO graph - advanced - field doesn't eat trailing space
Product: Wireshark
Version: 1.0.4
Platform: PC
OS/Version: Windows Vista
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: martinvisser99@xxxxxxxxx
Build Information:
Version 1.0.4 (SVN Rev 26501)
Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows Vista, build 6000, with WinPcap version 4.0.2 (packet.dll
version 4.0.0.1040), based on libpcap version 0.9.5, without AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
If you go to create an Advanced IO Graph (with calculated fields), if you enter
a field with a trailing space, Wirehsark reports an error. For instance if in
the field you enter "frame.len " as opposed to "frame.len", and attempt to
display the graph you get the following error "There is no field named
'frame.len '."
(I frequently copy and paste the field from a display filter entry box and
hence often inadvertantly add a trailing space)
The entry parser should strip leading and trailing whitespace.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.