Your statement is true.
But coredll doesn't support the DebugBreak api :
\network\x86> testapi coredll DebugBreak
coredll doesn't know about DebugBreak
\network\x86>
So could you explain what you want me to do about this bug report and why it would improve things ?
I am a bit puzzled but I have to admit that this (DebugBreak) is a strange API.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Defining it as a macro that expands to the well known x86 pseudo-instruction does make sense.
I will do that.
For the record :
- that's not the same thing as having it exported from coredll
- I don't want to copy a definition from Visual C++ : that would violate copyrights.
Thanks for the input
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your statement is true.
But coredll doesn't support the DebugBreak api :
\network\x86> testapi coredll DebugBreak
coredll doesn't know about DebugBreak
\network\x86>
So could you explain what you want me to do about this bug report and why it would improve things ?
I am a bit puzzled but I have to admit that this (DebugBreak) is a strange API.
DebugBreak() should be defined as a macro to something similar to __asm int 3 (expressed in gnu assembler, of course).
If you look into VC++ CE kfuncs.h, I'll see the definition of it for various targets.
Defining it as a macro that expands to the well known x86 pseudo-instruction does make sense.
I will do that.
For the record :
- that's not the same thing as having it exported from coredll
- I don't want to copy a definition from Visual C++ : that would violate copyrights.
Thanks for the input