Re: [osol-code] Is this a bug? (M_READ vs. FNDELAY)

2009-01-12 Thread Peter Memishian
> > Based on the M_READ definition in the original AT&T documentation, it > > seems like a bug to me. FWIW, it dates back to the introduction of > > M_READ in SVR3.2. > > Furthermore, upon examination of the code, the only driver I can find > that actually enables M_READ delivery is ecpp.

Re: [osol-code] Is this a bug? (M_READ vs. FNDELAY)

2009-01-12 Thread Garrett D'Amore
Peter Memishian wrote: > > I've noticed a problem, which I think might be a bug. It causes some > > grief for me with the Boomer project. > > > > Specifically, when a stream is opened as nonblocking (FNDELAY, > > O_NONBLOCK, etc.), I find that I no longer get M_READ notifications, > > ev

Re: [osol-code] Is this a bug? (M_READ vs. FNDELAY)

2009-01-12 Thread Peter Memishian
> I've noticed a problem, which I think might be a bug. It causes some > grief for me with the Boomer project. > > Specifically, when a stream is opened as nonblocking (FNDELAY, > O_NONBLOCK, etc.), I find that I no longer get M_READ notifications, > even when I've asked for them using

[osol-code] unwinding an exception frame

2009-01-12 Thread D.
So I wrote a user threads lib. The threads run in a Solaris process. Signals occur on the stack of whatever thread is currently executing. I get signals, like SIGINT, etc., and can let them unwind naturally. But I thought that I'd like to unwind the exception from within the exception handler, i

Re: [osol-code] Is this a bug? (M_READ vs. FNDELAY)

2009-01-12 Thread Garrett D'Amore
m...@bruningsystems.com wrote: > Hi Garrett, > > Garrett D'Amore wrote: > >> I've noticed a problem, which I think might be a bug. It causes some >> grief for me with the Boomer project. >> >> Specifically, when a stream is opened as nonblocking (FNDELAY, >> O_NONBLOCK, etc.), I find that I n

Re: [osol-code] Is this a bug? (M_READ vs. FNDELAY)

2009-01-12 Thread m...@bruningsystems.com
Hi Garrett, Garrett D'Amore wrote: > I've noticed a problem, which I think might be a bug. It causes some > grief for me with the Boomer project. > > Specifically, when a stream is opened as nonblocking (FNDELAY, > O_NONBLOCK, etc.), I find that I no longer get M_READ notifications, > even whe

Re: [osol-code] [opengrok] [pm-discuss] cv_wakeup() on src.opensolaris.org

2009-01-12 Thread Piotr Jasiukajtis
Trond Norbye pisze: > Vladimir Kotal wrote: >>> >>> I see what you mean. When I look at line 201 of condvar.c via vi, I >>> get cv_wakeup() as well. I wonder if this is somehow a stale cached >>> page? >>> >> >> Most probably stale cache entry on the server. Cc'ing the right >> mailing list to

Re: [osol-code] [opengrok] [pm-discuss] cv_wakeup() on src.opensolaris.org

2009-01-12 Thread Trond Norbye
Vladimir Kotal wrote: >> >> I see what you mean. When I look at line 201 of condvar.c via vi, I get >> cv_wakeup() as well. I wonder if this is somehow a stale cached page? >> > > Most probably stale cache entry on the server. Cc'ing the right mailing > list to report such issues (opengrok-d

[osol-code] Is this a bug? (M_READ vs. FNDELAY)

2009-01-12 Thread Garrett D'Amore
I've noticed a problem, which I think might be a bug. It causes some grief for me with the Boomer project. Specifically, when a stream is opened as nonblocking (FNDELAY, O_NONBLOCK, etc.), I find that I no longer get M_READ notifications, even when I've asked for them using M_SETOPTS and SO_MR

Re: [osol-code] [pm-discuss] cv_wakeup() on src.opensolaris.org

2009-01-12 Thread Vladimir Kotal
Eric Saxe wrote: > Piotr Jasiukajtis wrote: >> Hi, >> >> I don't know where to send it so please forgive me :) >> >> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/os/condvar.c#201 >> >> It should point to cv_wakeup(void *arg) function but it shows: >> >> 201 /* >>