ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 2587] Faulting application

Date: Wed, 4 Jun 2008 23:52:13 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2587





--- Comment #4 from Jaap Keuter <jaap.keuter@xxxxxxxxx>  2008-06-04 23:52:09 PDT ---
You're looking for a random problem which requires a long term capture. That
problem is better attacked by using dumpcap than wireshark. Dumpcap allows you
to do the capturing, without the dissection. So you do not run into resource or
other dissector problems, as you do now. I guess you have some external means
to determine the problem and time the problem occurs. Use that info to get back
to the capture files dumpcap writes out and load them into wireshark for
detailed analysis. 
Dumpcap is a commanline tool, so you'll need to open a command interpreter and
setup a commandline which tells dumpcap what to do. See the documentation for
the details.


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