https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4969
--- Comment #14 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-01-11 12:42:04 PST ---
(In reply to comment #13)
> I have loaded the dump file into windbg. What I determined from that is that
> the C RTL abort() function is being called within libglib. Hence the request
> for symbols or a debug build of libglib
OK, my apologies. Are you able to compile Wireshark yourself, run it, then
attach to it from the Microsoft Visual C++ debugger before attempting to
capture packets? That would hopefully yield more information than you're able
to obtain now.
Also, can you confirm if this is still a problem with 1.4.2, or even the latest
available automated revision, currently 35476, available from
http://www.wireshark.org/download/automated/win64/?
One other thing that confuses me (and which might be totally unrelated) is your
build information as it pertains to AirPcap:
... with PortAudio V19-devel (built Jun9 2010), with AirPcap.
^^^^^^^^^^^^
Running on 64-bit Windows 7, build 7600, with WinPcap version 4.1.2 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
^^^^^^^^^^^^^^^
So which is it? On my Windows XP 32-bit system, it is consistent and reads,
"with AirPcap", then "with AirPcap 4.1.1 build 1838.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
