> current_threadid is neither 0 or 1. I think that the 0 is the case > where the current thread has not been updated, but I'm not sure why > the test for 1. Should it instead be a test for -1 (the > initialisation value for the global variable) to check whether it has > been updated at all? If so, the attached patch corrects the test.
I've had a closer look at how GDB references threads, and I see that it uses -1 for "all threads" and 0 for "any thread". This makes me more confident that the patch attached to the previous email is correct - the function checks for thread IDs that refer to specific threads. Alan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
