| Bug ID |
9688
|
| Summary |
editcap: inconsistent usage of stdout vs. stderr
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.5
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Extras
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 12496 [details]
making sure that diagnostic messages go to stderr instead of stdout
Build Information:
wireshark 1.10.5 (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 GTK+ 2.20.1, with Cairo 1.8.8, with Pango 1.28.1, with
GLib 2.26.1, with libpcap, with libz 1.2.3, without POSIX capabilities, without
libnl, without SMI, without c-ares, without ADNS, without Lua, without Python,
without GnuTLS, without Gcrypt, without Kerberos, without GeoIP, without
PortAudio, with AirPcap.
Running on Linux 2.6.32-279.22.1.el6.x86_64, with locale en_GB.UTF-8, with
libpcap version 1.0.0, with libz 1.2.3, without AirPcap.
Intel(R) Core(TM) i5 CPU 660 @ 3.33GHz
Built using gcc 4.4.6 20120305 (Red Hat 4.4.6-4).
--
When I try to use editcap like this:
editcap -r -F libpcap valid_input.pcap /dev/stdout 1 | some_consumer
or
editcap -r -F libpcap valid_input.pcap - 1 | some_consumer
then "some_consumer" doesn't see a valid pcap-file because editcap puts some
diagnostic messages to /dev/stdout (whereas other ones it puts to /dev/stderr).
The attached patch changes this in the way that all diagnostic messages go to
/dev/stderr so that /dev/stdout can is free for cascaded piping (if necessary).
You are receiving this mail because:
- You are watching all bug changes.