Wireshark · Ethereal-users: [Ethereal-users] Small hang problem with 0.10.4 and FreeBSD 4.x when ending capture

[Pierre-Paul Lavoie <ppl@xxxxxxxxxxx>]

Hi,

	I'm having a problem similiar to what is described in FAQ
entry "Q 5.41: Ethereal hangs after I stop a capture.". I did turn
off name resolution but it didn't fix the problem.

	When capturing packets from an interface in ethereal (NIC
or loopback), pressing the stop button doesn't immidiatly stop
ethereal. From my observations, ethereal wait until a packet is
received.

	This gives me the impression that the code flow is blocked and is
waiting for an event from the interface to give back control
to the GUI code. The Expose events of ethereal are not process either.
The window doesn't get redrawn.

	I had the problem with 0.10.3 so I upgraded to 0.10.4. The
problem percist. Here's my current `ethereal -v` output.

ethereal 0.10.4
Compiled with GTK+ 2.4.0, with GLib 2.4.0, with libpcap 0.7, with libz 1.1.4,
with libpcre 4.5, with Net-SNMP 5.1.1, with ADNS.
Running with libpcap (version unknown) on FreeBSD 4.9-RELEASE.

	And here is the backtrace produced by an explicit SIGABRT.

#0  0x29272900 in __sys_poll () from /usr/lib/libc_r.so.4
#1  0x29271e4c in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4
#2  0x29271811 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4
#3  0x0 in ?? ()

	The machine is SMP running two AMD MP 2400+ processors.

	The interfaces have low traffic. So I must press "stop" and
generate some traffic to terminate the capture. I was
wondering if anyone is having the same problem or if this is a known
issue?

Thanks,
ppl