Jim Young
changed
bug 11702
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
CONFIRMED
|
| CC |
|
[email protected]
|
| Ever confirmed |
|
1
|
Comment # 2
on bug 11702
from Jim Young
Hello Carsten,
Did you by any chance first open and then close a capture file before leaving
Wireshark in the background?
I'm seeing a set a new set of messages logged once per second to the console[1]
after I close a capture file.
> C:\>12:05:09 Main Dbg Callback: Closing
> 12:05:09 Main Dbg Callback: Closed
> 12:05:10 Capture Dbg sync_interface_stats_open
> 12:05:10 Capture Dbg sync_pipe_open_command
> 12:05:11 Capture Dbg read from pipe 4: EOF (capture closed?)
> 12:05:11 Capture Dbg read 4 got an EOF
> 12:05:11 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:05:11 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.016s
> 12:05:12 Capture Dbg sync_interface_stats_open
> 12:05:12 Capture Dbg sync_pipe_open_command
> 12:05:12 Capture Dbg read from pipe 6: EOF (capture closed?)
> 12:05:12 Capture Dbg read 6 got an EOF
> 12:05:12 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:05:12 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.000s
> 12:05:13 Capture Dbg sync_interface_stats_open
> 12:05:13 Capture Dbg sync_pipe_open_command
> 12:05:13 Capture Dbg read from pipe 8: EOF (capture closed?)
> 12:05:13 Capture Dbg read 8 got an EOF
> 12:05:13 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:05:13 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.000s
The spark lines do not update after I have closed the capture file.
I do not recall seeing these messages clocked out before today. I see this on
botj master and on the same version you tested. I'm let the version you tested
run on my Windows 8.1 system and it crashed:
> 12:42:48 Capture Dbg read from pipe 2040: EOF (capture closed?)
> 12:42:48 Capture Dbg read 2040 got an EOF
> 12:42:48 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:42:48 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.004s
> 12:42:49 Capture Dbg sync_interface_stats_open
> 12:42:49 Capture Dbg sync_pipe_open_command
> 12:42:49 Capture Dbg read from pipe 2042: EOF (capture closed?)
> 12:42:49 Capture Dbg read 2042 got an EOF
> 12:42:49 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:42:49 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.006s
> 12:42:50 Capture Dbg sync_interface_stats_open
> 12:42:50 Capture Dbg sync_pipe_open_command
> 12:42:50 Capture Dbg read from pipe 2044: EOF (capture closed?)
> 12:42:50 Capture Dbg read 2044 got an EOF
> 12:42:50 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:42:50 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.003s
> 12:42:51 Capture Dbg sync_interface_stats_open
> 12:42:51 Capture Dbg sync_pipe_open_command
> 12:42:51 Capture Dbg read from pipe 2046: EOF (capture closed?)
> 12:42:51 Capture Dbg read 2046 got an EOF
> 12:42:51 Capture Dbg sync_pipe_wait_for_child: wait till child closed
> 12:42:51 Capture Dbg sync_pipe_wait_for_child: capture child closed after 0.004s
> 12:42:52 Capture Dbg sync_interface_stats_open
> 12:42:52 Capture Dbg sync_pipe_open_command
>
<Wireshark crashed at this point>
[1] - I have modified my Window's Wireshark preferences to enable the console
always and to enable debugging log levels.
> ####### User Interface ########
>
> # Open a console window (Windows only)
> # One of: NEVER, AUTOMATIC, ALWAYS
> # (case-insensitive).
> gui.console_open: ALWAYS
>
> # Log level
> # Console log level (for debugging)
> # A bitmask of log levels:
> # ERROR = 4
> # CRITICAL = 8
> # WARNING = 16
> # MESSAGE = 32
> # INFO = 64
> # DEBUG = 128
> console.log.level: 255
If I launch Wireshark directly from a CMD shell (something I do about 50% of
the time on Windows) then the log messages are written directly to the CMD
shell window and no console window is created.
You are receiving this mail because:
- You are watching all bug changes.
