It's a Win32 API function: http://msdn2.microsoft.com/en-us/library/aa363362.aspx
Outputs a string to the debugger. Lazarus is able to catch those messages, although the output in Lazarus is pretty dirty, and is somehow difficult to read. I supposed DebugLn would work the same way, but no :( Hope someday DebugLn will be connected to the debbuger. Regards! 2007/11/30, Mattias Gaertner <[EMAIL PROTECTED]>: > On Fri, 30 Nov 2007 10:27:43 -0600 > "Marco Alvarado" <[EMAIL PROTECTED]> wrote: > > > > > I saw the backtraces for the first time when testing the > > > > application from GDB. And now that makes me remember something I > > > > wanted to ask: I activate the "Debug output" window, but it > > > > doesn't show the lines generated by DebugLn(). > > > > > > Nope, debugger output is the internal logging of the lazarus > > > debugger. > > > > > > > But when I ran the application from GDB, the > > > > output of DebugLn() was shown. > > > > > > Consoleoutput is not (yet?) shown. > > > What you can do is start lazarus from a xterm. Then all is logged in > > > that terminal. > > > > I'm not sure if that's completely right, because OutputDebugString() > > works, but DebugLn() doesn't work. How is that possible? > > What is OutputDebugString? > > > Mattias > > _________________________________________________________________ > To unsubscribe: mail [EMAIL PROTECTED] with > "unsubscribe" as the Subject > archives at http://www.lazarus.freepascal.org/mailarchives > _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
