I tried, that, but couldn't find what the jdb command for getting the current thread is. Anyone?
/Staffan On 30 okt 2013, at 11:17, Mikael Auno <mikael.a...@oracle.com> wrote: > On 2013-10-29 15:41, Staffan Larsen wrote: >> This test fails if there are background threads that run while the >> test is running. I've modified the test to use the "trace" commands >> in jdb with the extra thread parameter. I have assumed that the main >> thread has thread id 1. "trace" with thread id behaves a little bit >> different so a couple of extra "cont" were needed. >> >> webrev: http://cr.openjdk.java.net/~sla/7145419/webrev.00/ > > Would it be possible to set a breakpoint in main (or some other known > location) to determine the thread id (as we do in some of the JDI tests) to > make sure we have the right one before continuing with the rest of the test? > > Mikael
