["Guy Harris" <gharris@xxxxxxxxx>]

Biot Olivier said:
> Regarding your new bug, I cannot reproduce it on my GTK2 Win32 build.
> Ethereal doesn't exit but the capture file is closed, that's all.

If you run Ethereal with a file name specified on the command line (with
or without the "-r" option), aborting the read causes Ethereal to exit. 
That's not a bug - it's at most a misfeature, as the code was written to
do that.

If you open a file from the GUI, aborting the read causes Ethereal to
close the file.

We could perhaps have Ethereal, in both cases, keep the frames that it's
read in, although it should probably pop up a message box warning that you
do *NOT* have the entire capture read in.

Note that if you arrange, in some GUI, to have Ethereal be the program run
when you double-click on a file (that can be done on Windows *AND* KDE
*AND* probably other UNIX+X desktop environments such as GNOME), it's run
with the file name specified on the command line - if you abort that read,
it seems pretty clearly wrong to me to close the file and leave Ethereal
running (as, in that case, you didn't just launch Ethereal just to have it
running, you asked to have that file open, which happened to be done by
running Ethereal) but the question is whether it should quit or leave the
file partially read.