Title: RE: [Ethereal-users] Ethereal on Linux
Ethereal was indeed running in "Update list of packets in real time" mode, the machine has 1.5GB swap space assigned. I will run the test again in standard mode and see how long it lasts.
GDB output if it helps futher :
(gdb) backtrace
#0 0x403e14e1 in __kill () from /lib/libc.so.6
#1 0x403e12ba in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x403e2a82 in abort () at ../sysdeps/generic/abort.c:88
#3 0x40296410 in g_logv () from /usr/lib/libglib-1.2.so.0
#4 0x402964c7 in g_log () from /usr/lib/libglib-1.2.so.0
#5 0x40294bcb in g_malloc () from /usr/lib/libglib-1.2.so.0
#6 0x4029513f in g_mem_chunk_alloc () from /usr/lib/libglib-1.2.so.0
#7 0x8133d9c in gtk_clist_get_selection_info ()
#8 0x812b8e2 in gtk_clist_clear ()
#9 0x812b6b2 in gtk_clist_append ()
#10 0x811a633 in finish_tail_cap_file ()
#11 0x811a886 in finish_tail_cap_file ()
#12 0x811a21b in continue_tail_cap_file ()
#13 0x8117f8c in do_capture ()
#14 0x4025f958 in gdk_io_invoke () from /usr/lib/libgdk-1.2.so.0
#15 0x402921a0 in g_io_unix_dispatch () from /usr/lib/libglib-1.2.so.0
#16 0x40293987 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0
#17 0x40294001 in g_main_iterate () from /usr/lib/libglib-1.2.so.0
#18 0x402941cc in g_main_run () from /usr/lib/libglib-1.2.so.0
#19 0x401aae57 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#20 0x813848f in main ()
#21 0x403d0b65 in __libc_start_main (main=0x81378e0 <main>, argc=1, ubp_av=0xbffffb44, init=0x8062d4c <_init>,
fini=0x816dc4c <_fini>, rtld_fini=0x4000df24 <_dl_fini>, stack_end=0xbffffb3c) at ../sysdeps/generic/libc-start.c:111
Rob
-----Original Message-----
From: Guy Harris [mailto:gharris@xxxxxxxxx]
Sent: 08 June 2001 10:56
To: Fulton, Robert [HAL02:HF63:EXCH]
Cc: ethereal-users@xxxxxxxxxxxx
Subject: Re: [Ethereal-users] Ethereal on Linux
On Fri, Jun 08, 2001 at 10:45:15AM +0100, Robert Fulton wrote:
> Can anybody tell me / help me work out what went wrong.
If the capture was running in "Update list of packets in real time"
mode, the problem is probably that the capture was too big for Ethereal
to handle - currently, the widget it uses to display the list of packets
consumes a *lot* of memory for large capture files; that may change in
the future.
If the capture was *not* running that mode, there might be a memory
leak. Try doing
gdb ethereal core
(with "ethereal" possibly replaced by the full pathname of the Ethereal
binary, although GDB appears to search your path for the binary to
debug), and then run the "backtrace" command and mail us the result of
that command.