Wireshark mailing list archives
Re: wireshark GUI vs tshark
From: Brian Oleksa <oleksab () darkcornersoftware com>
Date: Mon, 23 Nov 2009 12:02:17 -0500
Chris I have attached the error this time....sorry about that. :-) I get this error when I run with tshark using the following command:tshark -nr test.pcap ip.dst==x.x.x.x
But when I filter in the GUI ... I have no problems. Thanks, Brian Maynard, Chris wrote:
Any thoughts..??My first thought was, "I guess you forgot to include the error." :) In addition to the error, you might want to include some Wireshark version information, what OS you're running on and any other information that you think might be relevant. By the way, I tried a similar tshark command using Wireshark 1.2.4 on Windows XP SP3 with no problems. Maybe you are running an older version of Wireshark with a known bug that has been fixed, or maybe your test.pcap file is corrupt or exposes a Wireshark bug, in which case a bug report might be in order with the attached test.pcap file included so the core developers can analyze the error and find & fix the bug. - Chris -----Original Message----- From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Brian Oleksa Sent: Sunday, November 22, 2009 10:49 PM To: Developer support list for Wireshark Subject: [Wireshark-dev] wireshark GUI vs tshark WiresharkersWhen I use my dissector with the GUI... everything works fine. The pcap file that I load comes right up with NO problems. I can filter (ip.dst==x.x.x.x) with no problems.But if I try to open that same pcap file with tshark using the following command:tshark -nr test.pcap ip.dst==x.x.x.xThe files appears to start loading.. then I get the following error. Any thoughts..?? Thanks, Brian CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive thisemail in error, please delete it from your system immediately and notify us either by email, telephone or fax. You should not copy,forward, or otherwise disclose the content of the email. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- wireshark GUI vs tshark Brian Oleksa (Nov 22)
- Re: wireshark GUI vs tshark Maynard, Chris (Nov 22)
- Re: wireshark GUI vs tshark Brian Oleksa (Nov 23)
- Re: wireshark GUI vs tshark Jaap Keuter (Nov 23)
- Re: wireshark GUI vs tshark Brian Oleksa (Nov 23)
- Re: wireshark GUI vs tshark Maynard, Chris (Nov 23)
- Re: wireshark GUI vs tshark Brian Oleksa (Nov 23)
- Re: wireshark GUI vs tshark Jaap Keuter (Nov 23)
- Re: wireshark GUI vs tshark Brian Oleksa (Nov 23)
- Re: wireshark GUI vs tshark Jaap Keuter (Nov 23)
- Re: wireshark GUI vs tshark Brian Oleksa (Nov 24)
- Re: wireshark GUI vs tshark Maynard, Chris (Nov 24)
- Re: wireshark GUI vs tshark Jaap Keuter (Nov 24)
- Re: wireshark GUI vs tshark Brian Oleksa (Nov 23)
- Re: wireshark GUI vs tshark Maynard, Chris (Nov 22)