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-bugs: [Wireshark-bugs] [Bug 2587] Faulting application

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


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 4 Jun 2008 10:58:43 -0700 (PDT)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2587





--- Comment #3 from Ken Rudd <krudd@xxxxxxx>  2008-06-04 10:58:43 PDT ---
This fault occurs on all of my W2K3 SP2 i386 domain controllers. If a Max size
is set on the capture file, when it goes to roll over to a new file, Wireshark
faults.

I use max size, because if the capture gets abve about 250MB, the program
faults too, noting it is out of resources.

The captures get that large as I am tracing an elusive, random problem that
requires I leave the traces running  several days.

-Ken


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  • References:
    • [Wireshark-bugs] [Bug 2587] New: Faulting application
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 2587] Faulting application
  • Next by Date: [Wireshark-bugs] [Bug 2576] Packet-fc is not dissecting destination and source ID field properly
  • Previous by thread: [Wireshark-bugs] [Bug 2587] Faulting application
  • Next by thread: [Wireshark-bugs] [Bug 2587] Faulting application
  • Index(es):
    • Date
    • Thread

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