[tcpdump-workers] print-rx.c time format

2014-02-13 Thread Gisle Vanem
Building windump using MingW + gcc 4.7.2, I get: print-rx.c: In function 'fs_print': print-rx.c:929:4: warning: unknown conversion type character 'T' in format [-Wformat] print-rx.c:933:4: warning: unknown conversion type character 'T' in format [-Wformat] This comes from the macro

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Daniel H. Bahr
First of all thanks for your replies and sorry for the delay on mine. On what OS is this? Both Debian 7 and Ubuntu 12.04 (though I really think they represent the same to you). What type of processor is this running on? amd64 bit processors. The Ubuntu box runs on a QuadCore (the Debian one

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Daniel H. Bahr
This keeps getting weirder... Just unplugged the SIGSEGV signal to get a stacktrace upon its occurrence and I've performed 3 complete cycle (that is 2 packets) simulations without getting any buggy behavior. Is it at all possible that the Segment Violation signal that triggered the bailout

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Michael Richardson
The other thought I have is that java is heavily threaded, while libpcap is not thread safe. pcap_loop() is going to block. I see that your jni variable is a global... I wonder about that. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson,

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Guy Harris
On Feb 13, 2014, at 7:21 AM, Daniel H. Bahr dhb...@gmail.com wrote: This keeps getting weirder... Just unplugged the SIGSEGV signal to get a stacktrace upon its occurrence and I've performed 3 complete cycle (that is 2 packets) simulations without getting any buggy behavior. Is it

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Daniel H. Bahr
I see what you mean, but the native startSniffing method is invoked from a nested inner Thread. That is: Java Main Thread { do stuff... Nested Outer Thread { do more stuff... Nested Inner Thread { startSniffing here... } } } 2014-02-13 12:29 GMT-05:00, Michael

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Daniel H. Bahr
Guy, my previous reply was sent before I saw your last message. There IS a chance more than one instance of the Object owning the native methods would be created IF there would be need to sniff at several network interfaces simultaneously; in which case there would be a single instance of the

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Guy Harris
On Feb 13, 2014, at 10:23 AM, Daniel H. Bahr dhb...@gmail.com wrote: There IS a chance more than one instance of the Object owning the native methods would be created IF there would be need to sniff at several network interfaces simultaneously; in which case there would be a single instance

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Michael Richardson
Daniel H. Bahr dhb...@gmail.com wrote: my previous reply was sent before I saw your last message. There IS a chance more than one instance of the Object owning the native methods would be created IF there would be need to sniff at several network interfaces simultaneously; in

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Daniel H. Bahr
Well, I tried to debug the thing from eclipse but the crash could not be caught so I couldn't get the stack trace, I'll try and do that again later. For some reason, as I said earlier, if the SIGSEGV is not connected to the bailout nothing queer happens, I've run some large simulations and

Re: [tcpdump-workers] pcap segment violation

2014-02-13 Thread Guy Harris
On Feb 13, 2014, at 1:24 PM, Daniel H. Bahr dhb...@gmail.com wrote: For some reason, as I said earlier, if the SIGSEGV is not connected to the bailout nothing queer happens, Even if you leave SIGQUIT and SIGTERM connected? ___ tcpdump-workers