🚀 go-pugleaf

In article <9301112109.AA06983@deepthought.cs.utexas.edu>, pugsley@h32.nswc.navy.mil (Don Pugsley) writes:
|> 
|> My linker cannot find DebugOutput (L2029: Unresolved External)... a search
|> of all files in the \WINDEV tree finds NO occurences except DBAPI.TXT and
|> WINDOWS.H!  I am running the 3.1 debug version, have #included toolhelp.h
|> and windows.h, and have tried linking with OLDNAMES.LIB as suggested by the
|> Error Reference section on L2029.  Where is the code for this function
|> supposed to be? I am sure this is a simple problem but I am very
|> frustrated!  Thanks...

I had great problems with this too!! Eventually I got enough info from the net to get it to
work. Here goes:

First: add the following to the .DEF file (From: jjacob@nyx.UUCP)

IMPORTS
    _DebugOutput=KERNEL._DebugOutput
 
This will make the linkage work, but is not enough on it's own.

Second: for each call, 'OR' in DBF_APPLICATION to the first parameter
(From: rryan@panix.com): 

>I have a point in my code that calls OutputDebugString, DebugOutput,
>and then OutputDebugString again (3 successive lines).  The
>OutputDebugString strings are displayed by DBWin, but the DebugOutput
>string is not. I am using DBF_TRACE as the first parameter to
>DebugOutput

Ah ha.  You should use DebugOutput(DBF_TRACE | DBF_APPLICATION, ...).
That will do it.  It's not in the docs, but seems to work.

Third: If you are using DbWin, make sure that the application check box is checked.

Hope this helps, Jeremy

-- 
Jeremy Thorp, INMOS Ltd, 	|	jeremy@inmos.com
1000 Aztec West, Almondsbury, 	|	jeremy@inmos.co.uk
Bristol, BS12 4SQ, UK.		|	
Tel.  +44 454 616616    Fax. +44 454 617910
The above is the personal opinion of the author,
and does not necessarily reflect INMOS policy.