Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] OpcUa update

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 07 May 2007 10:37:57 -0700

Gerhard Gappmeier wrote:
> Hi,
> 
>> A fuzzed Sample.cap file (attached) crashed TShark and took a *very*
>> long time (2 mins) to load in WS.
>>
> it loads the file imediately on my computer without any delay.
> I tried the fuzzy file also with tshark.
> I called "tshark -r sample.cap", is this right?
> Because it didn't crash for me. I tried it several times.

You might try "tshark -rVx", which forces a packet detail hex dump
display for each packet.  If a bug is inside an "if (tree) { ... }"
block, then a simple "tshark -r" won't find it.

  • References:
    • Re: [Wireshark-dev] OpcUa update
      • From: Ulf Lamping
    • Re: [Wireshark-dev] OpcUa update
      • From: Gerhard Gappmeier
  • Prev by Date: Re: [Wireshark-dev] [Wireshark-commits]rev21705:/trunk//trunk/plugins/asn1/:asn1.hpacket-asn1.c/trunk/epan/dissectors/:packet-MAP_DialoguePDU.cpacket-acp133.cpacket-acse.cpacket-ansi_map.cpacket-ber.cpacket-ber.hpacket-camel.c ...
  • Next by Date: Re: [Wireshark-dev] OpcUa update
  • Previous by thread: Re: [Wireshark-dev] OpcUa update
  • Next by thread: Re: [Wireshark-dev] OpcUa update
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation