Problem with setting a vector might be: when do you look at it? If all goes well, all goes well. If all goes badly and powerpro locks up, there's no way to look at the trace vector.
However, can't hurt to try. Will do in a day or so. --- In [email protected], "brucexs" <bswit...@...> wrote: > > > What about debug calls right at various points in worker thread shutdown > > (.e.g called to clean up, completed cleanup and exiting) and then in dll > > shutdown to see if order of calls varies on different machines? > > BTW, would probably want to avoid doing actual I/O since it may screw up > ordering. Maybe set a static vector vector > nextwas[global_index++]=icode > where icode varies depending on point in code being traced. Could use > interlocked increment for global_index to be safe. Then output nextwas just > before dll exit. > > > > > > >
