Ethereal-dev: Re: [ethereal-dev] smb lanman core dump

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: "Marty Leisner" <leisner@xxxxxxxxxxxxxxxx>
Date: Tue, 21 Dec 1999 20:26:25 -0500
Which libc are you using?

I'm using libc-2.1.1...
I tried libc-2.1.2 with the same results...

Did you bug "\pipe\lanman response?"

I guess I'm going to have to look into it more...

If you're making a trace file,  would it be a reasonable idea to decouple
the tracing from the GUI -- I hate running GUI applications setuid root.
Also, it sometimes isn't very responsive...two programs might be very
useful (I like architectures which have a GUI part and a "work"
part).

Marty Leisner


Guy Harris <guy@xxxxxxxxxx> writes  on Tue, 21 Dec 1999 13:53:27 PST
     > > OK...I didn't even know it generated trace files...
     > 
     > When Ethereal is doing a packet capture, it writes the captured packets
     > to a file; when you hit the "Stop" button, it closes the capture file
     > and reads it in, as it would read in a file whose pathname was supplied
     > on the command line or in the "File:Open" dialog box.  (The "Update list
     > of packets in real time" stuff reads, instead, from the capture file as
     > it's being written.)
     > 
     > > Here's a trace which core dumps on redhat 6.0...
     > 
     > It didn't drop core when I tried it on an RH 6.0 system here, with
     > Ethereal 0.7.9.  There may be more to it....