tcpdump mailing list archives
Re: HP-UX crash on inject while receiving RESOLVED
From: "Harley Stenzel" <hstenzel () gmail com>
Date: Fri, 4 Aug 2006 10:55:28 -0400
On 7/31/06, Rick Jones <rick.jones2 () hp com> wrote:
I thought that one thread was send/recv and the other was send. The "send only" thread ostensibly would not need to be in promiscuous mode right?
Sort of. Promiscous mode on the NIC and promiscous on the STREAM are two different things. Libpcap always uses promiscous *stream*, even if the nic is not promiscous.
Still, do feel free to excercise your UX support contract and submit an ER against Streams to enable support for multiple promiscuous streams per interface.
I've inquired. Thanks. Also, it turns out that it was not a general libpcap limitation on HP-UX. There was too much on the stack, and the failure just happened to be in libpcap. One reader/writer and several writers does work on HP-UX. I was quite wrong when I thought the gdb strangeness was an artifact of the compiler or debugger -- it was the root problem. The reason gdb couldn't access the frame was the same reason that the program crashed.
rick jones
--Harley - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Current thread:
- Re: HP-UX crash on inject while receiving RESOLVED Harley Stenzel (Aug 13)