wireshark freezes when reading from pipe

This issue was migrated from bug 2082 in our old bug tracker.

Original bug information:

Reporter: Lucas Nussbaum
Status: RESOLVED FIXED
Product: Wireshark
Component: GTK+ UI
OS: Linux
Platform: x86
Version: 0.99.7

Lucas Nussbaum said:

Build Information: wireshark 0.99.7pre1

Copyright 1998-2007 Gerald Combs <gerald@‍wireshark.org> 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.1, with GLib 2.14.3, with libpcap 0.9.8, with libz 1.2.3.3, with libpcre 7.3, without SMI, with ADNS, without Lua, with GnuTLS 2.0.4, with Gcrypt 1.2.4, with MIT Kerberos, with PortAudio PortAudio V19-devel (built Oct 25 2007), without AirPcap.

Running on Linux 2.6.22-3-686, with libpcap version 0.9.8.

Built using gcc 4.2.3 20071014 (prerelease) (Debian 4.2.2-3).

---

Hi,

I'm trying to use a pipe to analyze what's going on on a remote host. I found http://wiki.wireshark.org/CaptureSetup/Pipes , but when I try:

wireshark -k -i <(ssh rxa tshark -w - not tcp port 22)

The wireshark window just freezes.
Capture works, according to what's displayed on stderr (packet count increases).

I also tried:

tshark -i <(ssh rxa tshark -w - not tcp port 22)

But it doesn't display anything, except what's sent written on stderr by the remote tshark instance, even after 300+ packets have been captured.

Any ideas?

added oslinux uigtk version0.x labels

Frederic Peters said:

For the record it worked fine with 0.99.6, maybe it is dumpcap related.

Lucas Nussbaum said:

I downgraded to 0.99.6, and can confirm that it works fine with that version.

Pavol Rusnak said:

Could not be related to bug #1740 (closed) ?

Lucas Nussbaum said:

Actually I can't reproduce that problem anymore with wireshark 1.0.2.

Gerald Combs said:

It looks like this problem might be related to the preferences code. If I try to read from a pipe when the preference file has errors, Wireshark hangs. If I open the preferences window and save (thereby creating a valid preferences file) everything works.

I can reliably replicate the problem with Wireshark 1.0.6 and 1.0.7 by adding an invalid line, e.g.

zzz.zzzzz: False

to the preferences file.

This doesn't appear to affect the trunk.

Jeff Morriss said:

Comment 4 says this problem no longer reproducible in 1.0.2. Comment 5 describes another problem but says it's fixed in trunk.

It appears there's nothing left to do, closing this.

closed

mentioned in issue #13406 (closed)