Hi list,
UNC paths without assigned drive letter are problematic in several
applications (e.g., the Poseidon UML tool doesn't "see" these and
double-clicking one will only launch the application but not open the file
on that "nonletter share").
It is possible that it's a GLib/GTK+ bug (or an undocumented "feature"), but
I cannot test this for now...
Best regards,
Olivier
----- Original Message -----
Subject: [Ethereal-bugs] [Bug 375] New: Crashes when saving to network
sharewithout drive letter mapping
http://bugs.ethereal.com/bugzilla/show_bug.cgi?id=375
Summary: Crashes when saving to network share without drive
letter mapping
Product: Ethereal
Version: 0.10.12
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Minor
Priority: Low
Component: Ethereal
AssignedTo: ethereal-bugs@xxxxxxxxxxxx
ReportedBy: adaig90@xxxxxxxxxxx
Build information:
Version 0.10.12 (C) 1998-2005 Gerald Combs <gerald@xxxxxxxxxxxx>
Compiled with GTK+ 2.4.14, with GLib 2.4.7, with WinPcap (version
unknown),
with libz 1.2.3, with libpcre 4.4, with Net-SNMP 5.2.1.2, with ADNS.
Running with WinPcap version 3.1 beta4 (packet.dll version 3, 1, 0, 24),
based on libpcap version 0.8.3 on Windows XP Service Pack 1, build 2600.
--
Windows XP allows users to create shortcuts (in "My Network Places") to
remote
shares without actually assigning a drive letter. The Ethereal "Open" and
"Save
As" dialogs do not appear to allow browsing to shares that do not have a
drive
letter assigned.
More importantly, however, Ethereal crashes when trying to save a trace
file
that has been directly opened from a network share with no drive letter.
To recreate this crash:
1. Add a network place under "My Network Places" or use an existing one,
just
make sure it is not located on a server that you already have mapped to a
drive
letter.
2. Place a .cap file into the share
3. From the Windows Explorer, navigate to the network share and
double-click the
.cap file. The trace will open in Ethereal.
4. Select "Save As..." from the File menu and Ethereal will immediately
crash to
the desktop with no error messages.
Of course the obvious work-around to this is to map a drive letter to the
network share, but it would be nice if Ethereal properly handled
non-mapped shares.