Custom Query (89 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 89)

Ticket Resolution Summary Owner Reporter
#273 fixed libpacketdump cannot decode the header following Linux SLL perry salcock
Description

Trying to run tracepktdump on the Wireless 1 trace results in the following output:

tracepktdump -c 1 pcapfile:/trace/wireless/1/wireless-i.pcap.gz 

Fri Mar  7 22:52:16 2008
 Capture: Packet Length: 178/178 Direction Value: 1
 Linux SLL: Packet Type = HOST
 Linux SLL: Hardware Address Type = 0x0323
 Linux SLL: Hardware Address Length = 6
 Linux SLL: Hardware Address = 00:00:02:7b:c4:7f
 Linux SLL: Protocol = 0x0019
tracepktdump: symbol lookup error: /home/salcock/install//lib/libpacketdump/link_6.so: undefined symbol: arphrd_type_to_libtrace

arphrd_type_to_libtrace is only defined locally within the libtrace library. The question is: do we want to make this an external function so that link_6.c can use it, or should we just copy and paste the code for that function into link_6.c and hope we never have to change it?

#274 fixed Libtrace fails to open some compressed files perry salcock
Description

Libtrace does not open compressed trace files created using crl_to_pcap (a libcoral tool). The error occurs when calling pcapfile_start() - attempting to read the pcap header returns Z_STREAM_END which is interpreted to be an EOF.

This generates the helpful error message of "Failed to start trace: No error" :)

There is a trace on wraith:/scratch/salcock/test2.gz which exhibits this behaviour if you need a test case.

#276 fixed rijndael.c makes gcc 4.4 very sad salcock salcock
Description

We do a crapload of nasty-looking casting in rijndael.c between uint8_t * and uint32_t *.

This tends to make new gcc's strict-aliasing warning go nuts, but actually fixing this is going to be more than a little tricky. Not just in terms of replacing the casts, but doing so in a way that won't actually break the code.

For example, it's not enough to do most of the casts once at the start of the function, because the pointer that they were cast from often gets incremented during the function. As a result, you need to redo the cast.

For now, I've disabled that warning for the traceanon tool. This is far from ideal, but hopefully this is just a case of gcc being whiny. At some point, though, the casting should be fixed and the warning re-instated.

Note: See TracQuery for help on using queries.