Kevin A. Burton - burtonator wrote: <snip>
>Could you describe the bug? > >It it is a timing bug you could use wait() in the right place in order to >magnify the incorrect timing interval. > >>For example, Trace.java has a static variable called iStop. If there are >>multiple databases running, then Database.execute() will allow 1 thread per >>Database to pass through, so you could have multiple threads in Database.java >>and also Trace.java. If the two threads hit "iStop++;" at the same time, then >>there could be a problem. How do you create a test to detect something like >>this? >> > >Is the pass designed in order to synchronize around iStop? > <snip> The general issue is that I need to get the threads to run "iStop++;" at the same time. The only way to come close to this is to put "wait()" right before the statement -- actually, I need the JVM to switch threads *on* this statement. I do not believe that it is possible to write a test that exposes this bug. -Clay _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
