Greetings.
After the recent u_intXX_t type elimination in tcpdump I did a test build on an
OpenIndiana x86_64 VM (which identifies itself as SunOS 5.11) and suddenly it
failed on the NFLOG test case. Interestingly, that test case not just used to
fail on OpenCSW Solaris 10 build servers during
On Apr 23, 2014, at 3:46 AM, Denis Ovsienko infrastat...@yandex.ru wrote:
Updating these headers to use uint_XX_t instead of u_intXX_t fixes respective
detection and the NFLOG test case in particular but it seems tcpdump should
tolerate the u_intXX_t types from libpcap for indefinitely
On Apr 23, 2014, at 10:24 AM, Guy Harris g...@alum.mit.edu wrote:
I made the change because a 64-bit build on Solaris 8 had to define u_int64_t
but defined it as unsigned long long int, which collided with the
%l[doux] that was used as the print format.
Probably the right thing to do
On Apr 23, 2014, at 6:58 AM, Philip Rosenberg-Watt
p.rosenberg-w...@cablelabs.com wrote:
I sent this to the list -- twice -- but it never showed up, so I'll just
resend it to you. I don't know what's going on.
Moderation? Michael?
I only put in the first if clause because some PON sniffer
Your request for analysis of the-tcpdump-group/libpcap is failed.
Analysis status: FAILURE
Please fix the error and upload the build again.
Error details:
Build uploaded has not been compiled fully. Please fix any compilation error.
You may have to run bin/cov-configure as described in the
Hi,
Please find the latest report on new defect(s) introduced to
the-tcpdump-group/libpcap found with Coverity Scan.
Defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 711715: Same on both sides (CONSTANT_EXPRESSION_RESULT)
/usr/include/x86_64-linux-gnu/bits/stdio2.h:
Your request for analysis of the-tcpdump-group/libpcap has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Your request for analysis of the-tcpdump-group/tcpdump has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Your request for analysis of the-tcpdump-group/libpcap has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Your request for analysis of the-tcpdump-group/tcpdump has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Your request for analysis of the-tcpdump-group/tcpdump has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Your request for analysis of the-tcpdump-group/libpcap has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Your request for analysis of the-tcpdump-group/tcpdump has been completed. The
results
should be available now at http://scan.coverity.com/
Please report any errors to scan-ad...@coverity.com.
___
tcpdump-workers mailing list
Guy Harris g...@alum.mit.edu wrote:
I sent this to the list -- twice -- but it never showed up, so I'll just
resend it to you. I don't know what's going on.
Moderation? Michael?
Nothing in the local queue.
Nothing in spam trap. That suggests that your email failed SPF or
On Apr 22, 2014, at 2:29 PM, Guy Harris g...@alum.mit.edu wrote:
In addition, the code *still* has a preference to indicate whether the octet
preceding the mode/LLID is just 0x55 or an encryption enabled/key ID field.
Either
1) there should be *two* LINKTYPE_ values -
On Apr 23, 2014, at 9:02 PM, Guy Harris g...@alum.mit.edu wrote:
So is there any technical reason *not* to dissect the frame by:
if that octet doesn't have the upper 6 bits as 010101, report it as an
error;
if that octet is 0x55, show it as a preamble octet, and treat the
16 matches
Mail list logo
