Wireshark-bugs: [Wireshark-bugs] [Bug 10488] Wireshark should let you work with multiple capture
Comment # 17
on bug 10488
from Guy Harris
(In reply to Tommaso Pecorella from comment #16)
> (In reply to Guy Harris from comment #15)
> > (In reply to Rajesh from comment #14)
> > > is there any plan to include this feature request in the upcoming releases?
> >
> > Nobody has, as far as I know, ever worked on this, and, as far as I know,
> > nobody's working on it now.
>
> The astonishing thing is that 8at least on MacOS) a workaround to this is as
> simple as a perl wrapper around a bash script.
That's not a workaround for "you don't have a single process that has multiple
files open", it's a workaround for "the Qt version of Wireshark, when packaged
as an OS X app bundle, doesn't let you double-click a file to open it if
there's already one instance of Wireshark running".
On Windows, the way the file manager/app launcher works is that double-clicking
on a document creates a new process running a copy of the app, launched with
the path to the file as its first argument, so you can have multiple Wireshark
captures open - just not all in the same process.
I think most of the free-software desktops for UN*X work the same way.
OS X is different here - it's expected that an OS X app can have multiple open
files and, if there's already an instance of an app running, double-clicking
(or otherwise opening through Launch Services, e.g. using the open command),
the app is sent an "open this file, too" message.
On OS X, the old GTK+ version of Wireshark consisted of a wrapper that launched
the X11 app; the wrapper would either exit as soon as the Wireshark binary was
launched, or would hang around but launch additional instances, so that you
could open multiple files, with different processes handling the different
files.
What Gerald's talking about is different - he's talking about handling all open
files in a single process on *all* platforms (although I have the impression
that we're not so unusual, in that regard, on Windows and other UN*Xes), and
using that to make it easier to implement operations that act on *multiple
separate* captures, such as comparing two capture files.
You are receiving this mail because:
- You are watching all bug changes.
