Bug ID |
9145
|
Summary |
openSAFETY: SSDO Abort codes are handled incorrectly
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
SVN
|
Hardware |
x86
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Wireshark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 11556 [details]
openSAFETY: SSDO Abort codes are handled incorrectly
Build Information:
TShark 1.11.0 (SVN Rev 51785 from master)
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.36.0, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.9.1, with
Lua
5.1, without Python, with GnuTLS 2.12.23, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.8.0-29-generic, with locale de_DE.UTF-8, with libpcap
version
1.3.0, with libz 1.2.7.
Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
Built using gcc 4.7.3.
--
SSDO Abort Codes have been handled incorrectly and also have been presented at
the wrong time for the wrong message IDs. This patch corrects that.
You are receiving this mail because:
- You are watching all bug changes.