http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1146
Summary: Various instances of wireshark reading from various
named pipes -> closing error
Product: Wireshark
Version: 0.99.3
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Blocker
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: Kitty.Janssens@xxxxxxxxxxx
Build Information:
--
--
>From within a c++ program, I create various named pipes and start up various
wireshark instances, each reading from a named pipe (-i option).
I can send messages in the named pipes and they come out on the correct
wireshark instance.
So, I :
Create pipe A, start wireshark to read from A
Create pipe B, start wireshark to read from B
Create pipe C, start wireshark to read from C
Send messages in the pipes A, B, C in any order -> OK, they come out on the
correct wireshark instance
Then I want close the named pipes.
It works when I use the following sequence :
Close pipe C, wireshark (C) stops it's capture
Close pipe B, wireshark (B) stops it's capture
Close pipe A, wireshark (A) stops it's capture
But if I first close a pipe that wasn't the last one created, e.g.
Close pipe A,
Close pipe B,
Close pipe C,
then wireshark doesn't stop it's capture (although the pipe it is started with
is closed and even deleted (unlink) ! )
When I force it to stop (pressing the stop button), I get the error "child
capture process died: Segmentation violation - core dumped" .
Wireshark A does stop the capture when all instances/pipes are gone that have
been created after A.
Could this be a bug ?
--
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.