On Tue, 2005-03-15 at 20:44, Robert Shearman wrote:
Paul Vriens wrote:
Hi,
After I found that one of the files still contained a debugchannel for riched20 (instead of richedit), I added both to see a trace (just for the fun of it).
This however raised an exception in ME_DumpDocument:
- Could the exception be because of the length of the TRACE string?
Yes. Use debugstr_a to restrict the string to a length that won't overflow the trace buffer. Rob
The problem seems to be that there are several TRACE statements that do not have an ending "\n" for good reason apparantly. How can we cope with that.
Someone debugging with a +all and and app using riched20 will 'always' trigger this exception.
Cheers,
Paul.