Wireshark · Ethereal-dev: Re: [ethereal-dev] Viewing packets while capturing...

[guy@xxxxxxxxxx (Guy Harris)]

> The question is:  Are we (Guy, et al) SURE that pthreads implemented in
> this manner won't accomplish what we need done - namely capturing and
> displaying data "at the same time"??

I'm not *sure* of anything, which is why I'm bringing this up as a
potential problem - "not sure they won't" is inequivalent to "sure they
will".

Is "libc_r" more than just thread safe in the sense *I* usually think of
"thread safe", i.e.  "you don't have to worry about thread B making a
call that e.g.  accesses some data structure if thread A is in the
middle of updating that data structure"? I.e., is it *also* "thread
safe" in the sense that it's safe for threads to make blocking system
calls, *including, say, "select()"*, without fear that they'll block the
entire process (which means that they're presumably not direct system
calls, but wrappers around system calls, or are special "non-blocking"
system calls, or something)?

This includes "read()"s from - and, if we're going to support sending
raw packets, possibly "write()"s to - "/dev/bpf", as well as socket
reads and writes.