Re: Using trace in tests

James McKenzie wrote: > Charles Davis wrote: > >> James McKenzie wrote: >> >> >>> Charles Davis wrote: >>> >>> James McKenzie wrote: > All: > > I'm asking a question again, don't 'shoot' me, but I've noticed the use > of

Re: Using trace in tests

Charles Davis wrote: > James McKenzie wrote: > >> Charles Davis wrote: >> >>> James McKenzie wrote: >>> >>> All: I'm asking a question again, don't 'shoot' me, but I've noticed the use of the trace() function in tests and I would like to use this to troubl

Re: Using trace in tests

James McKenzie wrote: > Charles Davis wrote: >> James McKenzie wrote: >> >>> All: >>> >>> I'm asking a question again, don't 'shoot' me, but I've noticed the use >>> of the trace() function in tests and I would like to use this to >>> troubleshoot what is incorrect in the EM_FORMATRANGE patch as

Re: Using trace in tests

Charles Davis wrote: > James McKenzie wrote: > >> All: >> >> I'm asking a question again, don't 'shoot' me, but I've noticed the use >> of the trace() function in tests and I would like to use this to >> troubleshoot what is incorrect in the EM_FORMATRANGE patch as it is not >> passing on MacOSX

Re: Using trace in tests

James McKenzie wrote: > All: > > I'm asking a question again, don't 'shoot' me, but I've noticed the use > of the trace() function in tests and I would like to use this to > troubleshoot what is incorrect in the EM_FORMATRANGE patch as it is not > passing on MacOSX builds. The test appears to pas

Using trace in tests

All: I'm asking a question again, don't 'shoot' me, but I've noticed the use of the trace() function in tests and I would like to use this to troubleshoot what is incorrect in the EM_FORMATRANGE patch as it is not passing on MacOSX builds. The test appears to pass on WindowsXP sp2 as the failures