| Bug ID |
9510
|
| Summary |
qtshark Packet list Protocol and Info columns are spastic
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.10.3 (SVN Rev Unknown from unknown)
Copyright 1998-2013 Gerald Combs <[email protected]> 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 (64-bit) with GLib 2.32.4, with libpcap, with libz 1.2.8, with POSIX
capabilities (Linux), with libnl 3, with SMI 0.4.8, without c-ares, without
ADNS, with Lua 5.1, without Python, with GnuTLS 2.12.23, with Gcrypt 1.5.3,
with
MIT Kerberos, without GeoIP.
Running on Linux 3.10.7-gentoo, with locale en_US.UTF-8, with libpcap version
1.3.0, with libz 1.2.8.
Intel(R) Xeon(R) CPU W3565 @ 3.20GHz
Built using gcc 4.6.3.
--
We have developed a set of dissectors for our protocols (which we will be
submitting for inclusion in Wireshark soon). One of the protocols is built on
TCP. The dissector sets the Protocol and Info columns. Some basic information
is put in the Info column, then the fence is set, allowing for additions to the
Info column (allowing for multiple messages in a single TCP PDU).
All of this behaves properly when using wireshark (GTK). When using qtshark
(Qt), the behavior is... odd.
- Initially, the Info column is correct, but the Protcol column is set to TCP
(we set it to LBT-TCP)
- As soon as I click ANYWHERE (like in the browser window as I'm creating this
bug report) the Info column gets changed to the regular TCP info (sport ->
dport [flags] Ack= and so forth) - BUT the data we've added after the fence is
preserved
- If I enter a filter _expression_, the Info column is once again correct - but
again as soon as I click anywhere it reverts to the regular TCP info plus what
we've added after the fence
- If I resize the Protocol column, the correct protocol appears (LBT-TCP in
this case) - but clicking anywhere causes the Protocol column to revert back to
TCP.
I would love to capture some screen shots to illustrate - but I haven't yet
figured out how without clicking somewhere else. Perhaps a video recording
would work.
I know the description is kinda sketchy. I'll work on trying to get more
concrete information, but I wanted to at least get this on the radar.
You are receiving this mail because:
- You are watching all bug changes.
