Wireshark mailing list archives
Re: Seg Fault - Creating new wiretap type
From: Chris Maynard <chris.maynard () gtech com>
Date: Fri, 22 Oct 2010 00:52:38 +0000 (UTC)
Alex Lindberg <alindber@...> writes:
That was my thought, however I used a debugger and printf statements to watch
the file handle passed to the wiretap routines. The file was the same in all cases. This has me stumped. You didn't mention which OS you were compiling on. With Windows, I've often run into problems that a distclean will resolve. Regardless of your platform, you might give it a try. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Seg Fault - Creating new wiretap type Alex Lindberg (Oct 21)
- Re: Seg Fault - Creating new wiretap type Stephen Fisher (Oct 21)
- Re: Seg Fault - Creating new wiretap type Alex Lindberg (Oct 21)
- Re: Seg Fault - Creating new wiretap type Chris Maynard (Oct 21)
- Re: Seg Fault - Creating new wiretap type Stephen Fisher (Oct 22)
- Re: Seg Fault - Creating new wiretap type Alex Lindberg (Oct 22)
- Re: Seg Fault - Creating new wiretap type Hadriel Kaplan (Oct 23)
- Re: Seg Fault - Creating new wiretap type - RESOLVED Alex Lindberg (Oct 24)
- Re: Seg Fault - Creating new wiretap type Alex Lindberg (Oct 21)
- Re: Seg Fault - Creating new wiretap type Stephen Fisher (Oct 21)