Wireshark mailing list archives
Re: tshark (Windows) not working
From: "Maynard, Chris" <Christopher.Maynard () GTECH COM>
Date: Tue, 11 May 2010 16:52:29 -0400
Well, I definitely got a different result this time: dumpcap.exe - Application Error The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read". Click OK to terminate the program Click on CANCEL to debug the program OK Cancel I'm trying to narrow down the problem in the debugger but having trouble finding a good place for a break point so far ... - Chris -----Original Message----- From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Guy Harris Sent: Tuesday, May 11, 2010 4:20 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] tshark (Windows) not working On May 11, 2010, at 1:10 PM, Maynard, Chris wrote:
I don't know where the problem lies but I suspect something to do with dumpcap.c, especially since there seem to have been a lot of changes to it recently. Anyway, I looked through some of the changes to that file and decided to try to roll back a little farther. Here's what I found: Everything worked fine with r32349 (2010-03-31). From there I performed a binary search to try to narrow it down, and in the end I found that it worked fine with r32544 (2010-04-23) but failed with r32688 (2010-05-06), so hopefully that helps narrow down the problem.
See what happens with r32761. ___________________________________________________________________________ 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 CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive this email in error, please delete it from your system immediately and notify us either by email, telephone or fax. You should not copy, forward, or otherwise disclose the content of the email. ___________________________________________________________________________ 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:
- Re: tshark (Windows) not working, (continued)
- Re: tshark (Windows) not working Maynard, Chris (May 10)
- Re: tshark (Windows) not working Maynard, Chris (May 10)
- Re: tshark (Windows) not working Bill Meier (May 10)
- Re: tshark (Windows) not working Maynard, Chris (May 10)
- Re: tshark (Windows) not working Maynard, Chris (May 10)
- Re: tshark (Windows) not working Gerald Combs (May 10)
- Re: tshark (Windows) not working Abhik Sarkar (May 10)
- Re: tshark (Windows) not working Abhik Sarkar (May 10)
- Re: tshark (Windows) not working Maynard, Chris (May 11)
- Re: tshark (Windows) not working Guy Harris (May 11)
- Re: tshark (Windows) not working Maynard, Chris (May 11)
- Re: tshark (Windows) not working Gerald Combs (May 11)
- Re: tshark (Windows) not working Guy Harris (May 11)
- Re: tshark (Windows) not working Maynard, Chris (May 11)
- Re: tshark (Windows) not working Abhik Sarkar (May 12)