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: [Wireshark-dev] Runtime error after a few hours of running

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


From: "Joshua (Shiwei) Zhao" <swzhao@xxxxxxxxx>
Date: Wed, 4 Feb 2009 16:03:31 -0800

I was running Wireshark to capture WLAN traffic for some long time. Every a few hours it crashes with a runtime error.
With the debug mode, I saw the following error messages:

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

The thread 'Win32 Thread' (0x102c) has exited with code 3 (0x3).

The program '[5132] wireshark.exe: Native' has exited with code 3 (0x3).

I was running Wireshark-1.0.4 with winpcap-4.0.2 under winxp.
Can someone give some clue?
 
Many thanks,
Joshua 
  • Follow-Ups:
    • Re: [Wireshark-dev] Runtime error after a few hours of running
      • From: Bill Meier
  • Prev by Date: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86
  • Next by Date: Re: [Wireshark-dev] Runtime error after a few hours of running
  • Previous by thread: [Wireshark-dev] Dumpcap, reporting closed file
  • Next by thread: Re: [Wireshark-dev] Runtime error after a few hours of running
  • Index(es):
    • Date
    • Thread

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