| Bug ID |
9294
|
| Summary |
oid routines do not have have unit tests
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Extras
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.11.1 (SVN Rev 52689 from /trunk)
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.3, with libpcap, with libz 1.2.7, without
POSIX
capabilities, without libnl, without SMI, without c-ares, without ADNS, with
Lua
5.1, without Python, without GnuTLS, with Gcrypt 1.5.3, without Kerberos, with
GeoIP.
Running on Linux 3.11.4-201.fc19.x86_64, with locale en_US.UTF-8, with libpcap
version 1.4.0, with libz 1.2.7.
AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
Built using gcc 4.8.1 20130603 (Red Hat 4.8.1-1).
--
There are currently no unit tests for the functions in oids.c even though these
are used for many different protocols. Automated unit testing would help
assure that any changes made did not result in breakage.
You are receiving this mail because:
- You are watching all bug changes.