Wireshark-bugs: [Wireshark-bugs] [Bug 2080] New: 2d save of "Save As foo.pcap" "Save As foo.pcap

Date: Sat, 8 Dec 2007 22:01:28 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2080

           Summary: 2d save of "Save As foo.pcap" "Save As foo.pcap"
                    sequence fails
           Product: Wireshark
           Version: 0.99.6
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: wmeier@xxxxxxxxxxx


Build Information:
Version 0.99.6a (SVN Rev 22276)

Compiled with GTK+ 2.10.12, with GLib 2.12.12, 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 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804
--
The following sequence fails on Windows Wireshark:

   a. Start Capture/capture some packets/Stop capture;
   b. "save as foo.pcap" (will be OK);
   c. "save as foo.pcap" again (will fail somewhat weirdly with a gtk popup
window  indicating "file exists" after the Windows "save as" popup & etc).

The reason is that the second "save as" fails when trying to unlink foo.pcap
before saving it via cf_save. (See win32_file_dlg.c and file.c). The unlink
fails because the file is still open from the first call to cf_save).

The problem also shows up when doing a "file open foo.pcap" and then a "file
save as foo.pcap".

This would seem to be a rather "special case" which I'm not sure how to
address;  Somehow detect that "save as <filename>" is to the currently open
<filename> ?

(See Bug #2055 for some related information)


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