Ethereal-dev: Re: [ethereal-dev] Ethereal on Solaris -- lexical scanner problem s.

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Gilbert Ramirez <gram@xxxxxxxxxx>
Date: Fri, 6 Aug 1999 10:02:57 -0500
On Thu, Aug 05, 1999 at 10:15:07PM -0500, Brown, Wes wrote:
> 
> 
> Here we go, the stack trace you requested.
> 
> Hm.  Wonder if it's because I ran out of RAM?  Seems somewhat unlikely,
> considering that machine has 4GB ...
> 
> Regards,
> Wes Brown
> 
> #0  0xef28800c in _libc_kill () from /usr/lib/libc.so.1
> #1  0xef23a4e8 in abort () from /usr/lib/libc.so.1
> #2  0xef568584 in g_logv (log_domain=0xef577368 "GLib",
>     log_level=G_LOG_LEVEL_ERROR, format=0x0, args1=0x6) at gmessages.c:389
> #3  0xef56861c in g_log (log_domain=0xef577368 "GLib",
>     log_level=G_LOG_LEVEL_ERROR,
>     format=0xef5771b0 "could not reallocate %lu bytes") at gmessages.c:406
> #4  0xef566988 in g_realloc (mem=0xef577368, size=3689871839) at gmem.c:342
> #5  0x58950 in buffer_assure_space (buffer=0xf3130, space=3689869315)
>     at buffer.c:85
> #6  0x56a58 in libpcap_read (wth=0xeda98) at libpcap.c:200

This is amazing. The libpcap_read is requesting 3,689,869,315 bytes for
a packet that size. Either libpcap_read (in wiretap) got really confused
about what it read in the pcap trace, or the pcap trace has some wrong
packet sizes in it.

What version of libpcap are you using?

--gilbert