[openbeos] get_next_thread_info() bug ??

  • From: François Revol <revol@xxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Mon, 26 Aug 2002 20:48:20 +0200 (MEST)

while updating my renice command (so that -f searched for all thread by names,
not only the first that matches), I tried to use 0 as the team_id in 
get_next_thread_info(), as described in the BeBook, and to my surprise it 
returns 0x80000005: Invalid argument. I even rebooted just in case I had
screwed up the kernel (I tried -1 before)... I tried 2 as team_id and it lists
the right threads, so I assume they forgot this special case.
Maybe it only happens in BONE ?
Weird...

François.


Other related posts: