From: Joshua Blanton (email@example.com)
Date: Tue, 21 Feb 2006 12:06:30 -0500 From: Joshua Blanton <firstname.lastname@example.org> Subject: Re: tcptrace-bugs Compile Problem + ns2 support Message-ID: <20060221170630.GG18694@mauser.ipx.ath.cx>
Ahmad Khayyat wrote:
> I was trying to use tcptrace to analyze ns2 trace files, but was getting
> (among other output):
> Checking for file format 'ns' (ns -- network simulator from LBL)
> File format is NOT 'ns'
> when I run "tcptrace -d <filename.tr>"
> I was using tcptrace version 6.6.1-1 from debian testing.
This is *probably* due to a bug in libpcap; if a file weren't in
pcap format, some versions of libpcap close the file descriptor
which broke tcptrace. This was fixed in a later version of
tcptrace... In any case, you don't want to use 6.6.1 because it's
horribly broken. It is unfortunate that debian is shipping 6.6.1.
> Before complaining, I decided to check out the latest version. I
> downloaded tcptrace 6.6.7 and did a "./configure" and then a "make", but
> unfortunately, "make" did not complete. It gives the following error
> while compiling the file "filt_scanner.c":
> ./filt_scanner.l: In function 'filtyywrap':
> ./filt_scanner.l:159: error: 'yytext_ptr' undeclared (first use in this
> ./filt_scanner.l:159: error: (Each undeclared identifier is reported
> only once
> ./filt_scanner.l:159: error: for each function it appears in.)
> make: *** [filt_scanner.o] Error 1
Hm, it looks like your version of flex doesn't like our scanner
file... Off the top of my head I don't know of a quick fix for
that - I see that my ubuntu box doesn't like that file either.
Perhaps a new version of flex chokes on the input (I thought it
might be gcc4, but I tried with gcc 3.4 as well and it fails too).
Hopefully someone else can track this down; if not, I'll try and
track it down when I get some free time.
> Please let me know if you need any further info. to diagnose the problem.
That was an excellent bug report - thanks.
> One more question, should tcptrace be able to read ns2 trace files
> directly or do I still need to apply a patch? I realize I have to
> separate sender from receiver events and run tcptrace on each alone, but
> do I need to do anything else to be able to analyze ns2 trace files
> using tcptrace?
Now that is a good question. :-) It *should* work - I hacked on it
some a while back, and last I left it I could analyze ns2 files.
That said, there are enough variations in ns2 input files that it's
entirely possible that it won't work for you; fortunately, the input
parsing code is pretty straightforward - if it doesn't work, see
ns.c... It shouldn't be hard to fix. :-) If you do find bugs in
the ns2 parsing, please let us know - we'd love patches, or concrete
bug reports, either one.
This archive was generated by hypermail 2.1.7 : 02/22/06 EST