Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 37857: /trunk/ /trunk/: dumpcap.c
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx>
Date: Sat, 2 Jul 2011 00:04:32 +0200
On Fri, Jul 01, 2011 at 02:46:29PM -0700, Gerald Combs wrote:
> On 7/1/11 1:07 PM, darkjames@xxxxxxxxxxxxx wrote:
> > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=37857
> > 
> > User: darkjames
> > Date: 2011/07/01 01:07 PM
> > 
> > Log:
> >  Catch system exceptions from pcap_open_live() :)
> 
> With this in place and without Cygwin's error_start environment variable
> set dumpcap crashes with an "Unspecified fatal error encountered,
> aborting." dialog followed by a "Runtime Error!" dialog.

On all Windows machines or on buildbot?
I don't have access to windows machine right now, and I've copied exception handling 
from some other wireshark code.

Buildbot log prints some Access violation error /0xc0000005 -> STATUS_ACCESS_VIOLATION/
#v+
4.1.3 Step: Capture via stdin --> ./testout.txt
   14:35:39 CaptureChild Err  Exception from pcap_open_live(): 0xc0000005 (0x7f)
#v-

I've added some more debug in r37861, but well if it fails only in buildbot...
I don't care much, especially when it's AV which is quite hard to debug without (memory) debuggers.