Wireshark-dev: Re: [Wireshark-dev] Current trunk crashes on Windows?
From: "RUOFF LARS" <Lars.Ruoff@xxxxxxxxxxxxxxxxx>
Date: Wed, 14 Oct 2009 14:48:14 +0200
Yes, that helped. Thanks Mike. I guess i mixed things up between building from command line and via the provided VC++ workspace. That is an excellent idea by the way. (but i would have prefered that the default build command would have been "nmake -f Makefile.nmake" instead of "nmake -f Makefile.nmake setup all", which erases all the libs and starts downloading them all over again. :-/ ) Lars > -----Original Message----- > From: wireshark-dev-bounces@xxxxxxxxxxxxx > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of > Speck Michael EHWG AVL/GAE > Sent: mercredi 14 octobre 2009 13:15 > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Current trunk crashes on Windows? > > Hi Lars, > > some weeks ago I had the same problem that Wireshark crashes > at the same position as you described. > For me it helped to run "make distclean" and compile > everything from scratch again. > > > Cheers > Mike > > > > > -----Original Message----- > From: wireshark-dev-bounces@xxxxxxxxxxxxx > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of RUOFF LARS > Sent: Mittwoch, 14. Oktober 2009 10:13 > To: Developer support list for Wireshark > Subject: [Wireshark-dev] Current trunk crashes on Windows? > > Hi, > The current trunk (rev.30555) crashes on Windows when loading > the Prefs > file: > > Unhandled exception at 0x77c478ac in wireshark.exe: > 0xC0000005: Access violation reading location 0x00000001. > > Call Stack: > msvcrt.dll!77c478ac() > [Frames below may be incorrect and/or missing, no symbols loaded > for msvcrt.dll] > msvcrt.dll!77c2c2e3() > > wireshark.exe!font_init() Line 407 + 0xe bytes C > wireshark.exe!main(int argc=0, char * * argv=0x02ef5eac) Line > 2546 C > wireshark.exe!WinMain(HINSTANCE__ * > hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, > char * lpszCmdLine=0x00151f28, > int nCmdShow=1) Line 2806 + 0x17 bytes C > wireshark.exe!__tmainCRTStartup() Line 578 + 0x1d bytes C > kernel32.dll!7c816fe7() > > Is it just me? > Is it a known issue? > 1.3.0 runs fine when i compile from source. > > Lars > > For info: > > wireshark.exe -v > wireshark 1.3.1 > > Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and > contributors. > This is free software; see the source for copying conditions. > There is NO warranty; not even for MERCHANTABILITY or FITNESS > FOR A PARTICULAR PURPOSE. > > Compiled with GTK+ 2.16.6, with GLib 2.20.5, with WinPcap > (version unknown), with libz 1.2.3, without POSIX > capabilities, with libpcre 7.0, with SMI 0.4.8, with c-ares > 1.6.0, with Lua 5.1, without Python, with GnuTLS 2.8.1, with > Gcrypt 1.4.4, with MIT Kerberos, with GeoIP, with PortAudio > V19-devel (built Sep 23 2009), with AirPcap, with new_packet_list. > > Running on Windows XP Service Pack 2, build 2600, with WinPcap version > 4.0.2 > (packet.dll version 4.0.0.1040), based on libpcap version > 0.9.5, GnuTLS 2.8.1, Gcrypt 1.4.4, without AirPcap. > > Built using Microsoft Visual C++ 9.0 build 30729 > ______________________________________________________________ > __________ > ___ > Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe > ______________________________________________________________ > _____________ > Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe >
- References:
- [Wireshark-dev] Current trunk crashes on Windows?
- From: RUOFF LARS
- Re: [Wireshark-dev] Current trunk crashes on Windows?
- From: Speck Michael EHWG AVL/GAE
- [Wireshark-dev] Current trunk crashes on Windows?
- Prev by Date: Re: [Wireshark-dev] VoIP Calls and -Graph dialog behaviour
- Next by Date: Re: [Wireshark-dev] VoIP Calls and -Graph dialog behaviour
- Previous by thread: Re: [Wireshark-dev] Current trunk crashes on Windows?
- Next by thread: Re: [Wireshark-dev] VoIP Calls and -Graph dialog behaviour
- Index(es):