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 everything works out fine, as opposed as when I connect the signal in which case it crashes every time. I'll also take a look at the "singleton" *jni and see how to work that around. Best regards to everyone 2014-02-13 16:16 GMT-05:00, Michael Richardson <m...@sandelman.ca>: > > 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 which case there would > > be a single instance of the class for each network interface to be > > sniffed. > > > Could this raise the issues you mention above? > > You have only one *jni variable, that might be a problem if it will be > different in different threads/contexts. > > -- > ] Never tell me the odds! | ipv6 mesh networks > [ > ] Michael Richardson, Sandelman Software Works | network architect > [ > ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails > [ > > > > _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
