> > Hi! Wireshark just crashed "segmentation fault", so I can't tell for
> > the long trace, unless its possible to extract from the file logged
> > to disk...............
>
> Unfortunately, it's not; libpcap capture format (Wireshark's native
> format) doesn't have any provision for storing packet-drop statistics.
>
> Did Wireshark leave a core dump file? If so, can you run gdb with the
> Wireshark binary and the core file, and run the "backtrace" command to
> get a stack trace?
>
Will be happy to help.................where should the file be and how is it called? No file in the captured directory.............
> Does Wireshark crash if you try to read the file logged to disk?
Loading it now.............not crashed yet..........will report if it does!
> > I ran a short 4min 10000 packet trace and 0 packets "Lost" at the
> > bottom of the screen.
>
> "Lost" presumably meaning "Dropped", as that's the word Wireshark uses.
Yes! sorry about that! also, 0 dropped with a 40000 packettrace.
What else could be causing the discrepancy..............?
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
Windows Live™: E-mail. Chat. Share. Get more ways to connect. See how it works.
|