Todd,
I've looked at the code and I've found something interesting...
I think you're right... something like
pnip = pnip->myNext
seems to be required....
On Fri, 17 Mar 2000, Todd L. Miller wrote:
> In scheduler::checkPendingNotifies(), the CVS version (I believe
> the copy I'm looking at is the recent one), does anyone else find it odd
> that the terminating condition is (pnip->myNext != NULL) yet pnip -- so
> far as I can tell -- is never changed? Could someone who's got an intact
> CVS tree point the debugger at this and figure out why the loop
> terminates? (Is my copy of scheduler.cc right? Are the jbSLL items not
> set up right, e.g. myNext is always NULL? Is the list of pending notifies
> always empty (despite addPendingNotify() being called from threadable.cc?)
> Have we, for some reason, only ever had a single thread in the pending
> queue?) I'm asking because I just finished moving that code to the 'new'
> scheduler, and realized, contrary to the comment, that it never did walk
> the list, and I wanted to find out what was going on. Thanks.
>
> -_Quinn
>
>
>
> _______________________________________________
> Kernel maillist - [EMAIL PROTECTED]
> http://jos.org/mailman/listinfo/kernel
--
======================================================
Eng. Corrado Santoro - PhD Student
Unversity of Catania - Engineering Faculty
Institute of Computer Science and Telecommunications
Viale A. Doria, 6 - 95125 CATANIA (ITALY)
Tel: +39 095 7382365 Fax: +39 095 7382397
EMail: [EMAIL PROTECTED]
Personal Home Page:
http://www.cdc.unict.it/~csanto
ARCA Mobile Agent Framework Home Page:
http://osweb.iit.unict.it/ARCA
======================================================
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
