Wireshark mailing list archives
Re: Help Me To Solve The Problem
From: lie zheng <lippzl () hotmail com>
Date: Tue, 27 Apr 2010 09:43:39 +0800
Hi, Thanks a lot. I will check the source file about wireshark. But I still don't understand that I build *the same source tree* without my plug-in and it couldn' work. And more about the development of my version is as follows: Version 0.99.5-lipps123 Copyright 1998-2007 Gerald Combs <gerald () wireshark org> 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.10.7, with GLib 2.12.7, with WinPcap (version unknown), with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio PortAudio V19-devel, with AirPcap. Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1 (packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b (20091008), without AirPcap. Built using Microsoft Visual C++ 7.10 build 3077 Wireshark is Open Source Software released under the GNU General Public License. Check the man page and http://www.wireshark.org for more information. Any suggestion, I would like it. Thanks. Lippman
Date: Sun, 25 Apr 2010 16:05:06 -0600 From: steve () stephen-fisher com To: wireshark-dev () wireshark org Subject: Re: [Wireshark-dev] Help Me To Solve The Problem On Thu, Apr 22, 2010 at 04:32:05PM +0800, lie zheng wrote:One error dialog box which displayed some information " The file "C:\DOCUME~1\zheng\LOCALS~1\Temp\etherXXXX" could not be opened for some unknown reason." happend.This error message comes from capture_info.c under the case WTAP_ERR_CANT_OPEN for the variable err, which is being called from capture_info_new_file() in the same source file, which is probably being called from wiretap/file_access.c. There are numerous reasons capture_info_new_file would fail and return NULL; take a look at wiretap/.file_access.c and see if any of those could be the problem. My first guess would be a file permissions issue. What does your plug-in do? If you can build *the same source tree* without your plug-in and it works, then look at the plug-in. Don't compare a downloaded version of Wireshark to your local source tree minus your plug-in. -- Steve ___________________________________________________________________________ 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
_________________________________________________________________ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. https://signup.live.com/signup.aspx?id=60969
___________________________________________________________________________ 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:
- Help Me To Solve The Problem lie zheng (Apr 22)
- Re: Help Me To Solve The Problem Maynard, Chris (Apr 22)
- Re: Help Me To Solve The Problem lie zheng (Apr 22)
- Re: Help Me To Solve The Problem Maynard, Chris (Apr 22)
- Re: Help Me To Solve The Problem lie zheng (Apr 26)
- Re: Help Me To Solve The Problem lie zheng (Apr 22)
- Re: Help Me To Solve The Problem Maynard, Chris (Apr 22)
- Re: Help Me To Solve The Problem Stephen Fisher (Apr 25)
- Re: Help Me To Solve The Problem lie zheng (Apr 26)
- Re: Help Me To Solve The Problem Maynard, Chris (Apr 26)
- Re: Help Me To Solve The Problem lie zheng (Apr 26)