Tools APIDebugger |
|
Open Tools API
|
The debugger interfaces are brand new in the new API. They don't all
work, though. In particular, the debugger notifier interface doesn't work, and without it,
the remaining debugger interfaces aren't much use. If you're desperate, you can hack
around the limitations a little bit. For example, instead of using the Run>Run
command to start your debugging session, create a wizard that defines a new Run menu item.
Your wizard can call Once your wizard has defined its initial process notifiers, they work correctly, and you can define thread notifiers when the processes create threads, and define process module notifiers if they strike your fancy.
If you dare to use the breakpoint interfaces, watch out! When the user modifies a breakpoint, Delphi frees the old interface and creates a new one. Because the debugger notifier doesn't work, your wizard has no way of knowing when this happens. Also, everytim I use the Because of all these problems, I haven't used the debugger interfaces much. One more thing. If you access a thread's context to get to the FPU state, each number's exponent is stored on the opposite end of the number from what you might expect. To convert the context value to a valid floating point number, you must move the exponent to the other side, then convert it to a floating point number. |
Copyright © 1998 Tempest Software, Inc. All rights reserved.