Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 5939] Access Violation passing data from CACE Pilot to Wireshark.

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5939

--- Comment #5 from tinsleyjt@xxxxxxxxxxx 2011-05-23 06:50:31 PDT ---
(In reply to comment #4)
> (In reply to comment #2)
> > Gerald checked in a fix for a dumpcap bug in r37341. If Pilot is using pipes,
> > that might
> > fix your issue. Can you retest with a build r37341 or later and report if the
> > problem
> > still persist?
> 
> Tried with version (wireshark-win32-1.7.0-SVN-37356.exe) problem still persists. Stack for dumpcap.exe below. 
> What other details do you need?
> 
> ntoskrnl.exe!KiSwapContext+0x2f
> ntoskrnl.exe!KiSwapThread+0x8a
> ntoskrnl.exe!KeWaitForSingleObject+0x1c2
> ntoskrnl.exe!KiSuspendThread+0x18
> ntoskrnl.exe!KiDeliverApc+0x124
> ntoskrnl.exe!KiSwapThread+0xa8
> ntoskrnl.exe!KeWaitForSingleObject+0x1c2
> ntoskrnl.exe!NtWaitForSingleObject+0x9a
> ntoskrnl.exe!KiFastCallEntry+0xfc
> ntdll.dll!KiFastSystemCallRet
> ntdll.dll!NtWaitForSingleObject+0xc
> kernel32.dll!WaitForSingleObjectEx+0xa8
> kernel32.dll!WaitForSingleObject+0x12
> libgthread-2.0-0.dll+0x23e1
> libgthread-2.0-0.dll+0x260f
> libglib-2.0-0.dll!g_byte_array_sort_with_data+0x13f
> libglib-2.0-0.dll!g_async_queue_timed_pop+0x39
> dumpcap.exe+0x952f
> dumpcap.exe+0x9388
> dumpcap.exe+0x77b7
> dumpcap.exe+0x5f5e
> dumpcap.exe+0xd793
> kernel32.dll!BaseProcessStart+0x23

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.