🚀 go-pugleaf

"Brent" <nospam@nospam.com> wrote in message
news:3f610680@newsgroups.borland.com...

> The lParam points to the address of a DEBUGHOOKINFO
> structure.  How do I get the 'data' from this structure and pass
> it onto the CallNextHookEx function?

You're not supposed to be handling WH_DEBUG that way at all.  What exactly
are you trying to accomplish by tricking the system into calling hooks
directly?

The DEBUGHOOKINFO is meant to be used for "peeking" at the data that will be
sent to the real hook which is about to be called.  That is all a WH_DEBUG
hook should be doing.  It is used for diagostics and logging purposes.  The
hook procedure is not even allowed to modify the values in the DEBUGHOOKINFO
structure.

When it comes to calling CallNextHookEx(), WH_DEBUG is still a hook like any
other.  You are supposed to be calling the next hook in the WH_DEBUG chain,
not the real hook directly.  As such, you should be passing the same HHOOK,
wParam and lParam values that were sent to your own WH_DEBUG procedure, not
the wParam and lParam that are inside of the DEBUGHOOKINFO.  In other words,
change this line:

    return CallNextHookEx(HDebugHook, hookInfo->code, hookInfo->wParam,
hookInfo->lParam);

To this instead:

    return CallNextHookEx(hHook, Code, wParam, lParam);

Where hHook is your own HHOOK for the WH_DEBUG hook itself.


Gambit


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.515 / Virus Database: 313 - Release Date: 9/1/03