Peter Dons Tychsen wrote:
By browsing MSDN, i found out that i can accomplish this by using the documented function StalkWalk64(), which can examine the call stack. I would then introduce this into the test system for DLLs like "user32". By running the test on original Windows we could know which messages we are incorrectly "posting" or "sending" where it should have been the opposite. This could fix some vital issues.
I don't think there is a problem as i am just using documented APIs from MSDN, but since it includes looking at the call stack, i was curious if there might be a legal problem.
I don't want to put the idea to use or release it if it in any way is illegal.
Please think long and hard before you reply.
DMCA Reverse engineering exemption:
http://www.chillingeffects.org/reverse/faq.cgi#QID210
regards, Jakob