Hi Viktor, > I'd appreciate if you could describe it, as I don't have such > official debugger on my system, I used DbgView() for tests.
The windbg in a component of "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1" / "Debugging tools for Windows". Dbgview is just a very useful viewer. I tested it and I cannot see any differences comparing with the previous solution without CR/LF insertion. If it is necessary we can generate here a flexible solution with and without CR/LF, selectable by the existing HB_TR_WINOUT envvar. > If extra line ending (/r or /n or both) is required for windbg, > it's easy to add it to printf() calls, although I'm still not > sure why ending space trimming is required, or in which calls > does this exactly causes problems. An any optimized solution is welcome, with the original solution the debug messages are shown without line-feeds. > You're right, now it's clear. In this case the solution is to replace > HB_TCHAR_* macros with something native. I'll try to do it. We need here a general solution taking into consideration the all possible situations when HB_TRACE is called indirectly in HB_TRACE. Best regards, István _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
