|
> I want to do it without making a wrapper, and without hooking GetProcAddress ...
You have to modify the entry point of the original function so that it first executes a JMP instruction to your implementation.
Check this link:
http://www.fengyuan.com/article/wmprint.html[^]
There you will find a nice user32!BeginPaint hook implementation. However, because most user32 and kernel32 functions call an appropriate function in ntdll.dll, rather than executing the 0x2E interrupt directly (like BeginPaint does), your implementation will probably differ somewhat too; it will always depend on how the entry point of the original function looks like.
More useful links:
1. Intel OpCodes[^]
2. Api Hooking Revealed[^]
3. API Spying Techniques for Windows 9x, NT and 2000 [^]
Regards,
RK
|
|
|
|
|
Hi!
How can i handle the click over a system tray baloon tip?
Thanks for your answer!
|
|
|
|
|
Hi,
check out this article. Beyond your question it provides a handy class to use message balloons in the system tray.
Peter Molnar
|
|
|
|
|
|
|
I am trying to create my first a multi-threaded dev-studio library project.
Is there a way to register a thread "cleanup" function that gets called each time a thread exits?
Here are some constraints for any suggestions you provide me:
1) I think I want my library statically linked. I see that for DLLs, DllMain() gets called each time a thread "detaches". This might be an appropriate place for me to stick my clean-up code if I were writing a DLL, but I don't think I want a DLL.
2) I don't want users of my library to have to write any code to get the cleanup function called. It should all be completely hidden.
3) I really only need my cleanup function executed for exiting threads that previously used particular functions from my library. So I do have a place to register the thread-exit function if there is a way to do that at all.
Thanks much for your help.
Matt Busche
|
|
|
|
|
> Is there a way to register a thread "cleanup" function
> that gets called each time a thread exits?
Hm..the first solution that comes to my mind: Call GetExitCodeThread periodically.
DWORD dwExitCode;
GetExitCodeThread( hThread, &dwExitCode);
if( dwExitCode == STILL_ACTIVE )
else
Anyway, why don't you simply call the cleanup routine at the end of ThreadFunc (just before calling return)?
DWORD WINAPI ThreadFunc( LPVOID lpParameter )
{
MyCleanUpRoutine();
return 0;
}Regards,
RK
|
|
|
|
|
Robert,
I guess I'm not a big fan of polling. As for your second suggestion: I'm trying to write a library that other developers will use. My library won't be spawning threads -- the application written by someone else will. So to pursue your suggestion, I'd have to include in my library notes, "oh, and be sure to call MyCleanUpRoutine() before your thread exits. Don't really care for that either. I guess I'm going to have to figure out how to get a DLL to work for me instead.
Actually, I think a DLL will work for me, but my initial attempts to create a DLL have not gone so well -- having problems getting global data from the DLL to link. 
Thanks much for your response.
Matt Busche
|
|
|
|
|
A *.dll would perfectly suit your needs. What you have to do is:
1.Create a *.dll and export all the functions you want your users to call
2.Make sure that the global data (if any) that simultanious threads can access (i.e. if two or more users at a time call the same function) is protected with syncronization objects like Critical sections
3.If your user calls LoadLibrary, your DllMain gets called with DLL_PROCESS_ATTACH, do some initialization, maybe keep reference count of attached clients, when your user calls FreeLibrary your DllMain gets called with reason DLL_PROCESS_DETACH. This is the place to call your CleanUpFunction()
Summary: your user has only to call LoadLibrary on your *.dll, GetProcAddress on the function, and FreeLibrary to get detached from your lib.
Peter Molnar
|
|
|
|
|
Peter,
Thanks for your reply. I actually started to do this and only just now discovered that this only works for RUN-TIME dynamic-linking of a DLL. (I.e., where you use the LoadLibrary call just like you said.) I saw some sample code on how to use LoadLibrary and GetProcAddress to call a single simple function from a DLL, but I'm not exporting a single simple function, I'm exporting a handfull of C++ concrete and abstract classes (along with all their numerous member methods and overloaded operators). It is not clear to me how you'd use run-time linking for such a library. Supppose Peter, you inherited from one of my abstract base-classes, then when you wrote your constructor, how would you call my base class constructor that is exported from my DLL?
And even if it's possible, my whole objective is to make my software as easy as possible to use. I certainly wouldn't want my users to have to jump through any flaming hoops to call a base class constructor or call the "=" operator for a class.
Here's a thought. What if I had two libraries? Library ALPHA has all my user visible software and could be built arbitrarily for either dynamic or static linkage. If built as a DLL it would be expected to be used with load-time dynamic-linkage. DLL BETA has nothing in it but a DllMain. Now, here's the trick: suppose DLL ALPHA secretly does a LoadLibrary call on BETA via some singleton constructor found in ALPHA. This singleton is instantiated the first time a user of ALHPA references resources that require thread initialization and cleanup activities. Then, I would presume that every subsequent thread spawn and delete would cause this DllMain in BETA to be invoked, would it not? I presume also that DllMain in BETA could invoke methods defined in ALPHA (to effect thread initialization and cleanup.)
I'm going to investigate this idea further and maybe try it out.
Let me know if I misunderstood the implications of your email. I've been battling this silly problem for a week now. If I don't come up with a better solution soon, I'll have to simply publish a threadCleanup method that must be called by users of my library on thread exit, but I really don't want to have to do this.
Once again, thanks sincerely for your help.
Matt
|
|
|
|
|
Peter,
OK, forget what I just wrote. If just found some words in the MSDN that would seem to imply that DllMain is used even if you use load time dynamic linking of the library. (Which I guess means that LoadLibrary must be invoked for you if you use load-time dynamic linking?)
Let me know if I'm lost. Let me know if I'm not lost. I'm forging ahead.
Matt
|
|
|
|
|
Hi
I have an application running with 2 forms.
however when i run it i get the following error:
c:\.......\stdafx.obj': <unknown>
Possible cause
If the message says "bad file number", the file may have been closing in the foreground while compiling in the background.
it seams there is a problem with #include "StdAfx.h"
at the begining of my plc.cpp class file. I have plc.h, and plc.cpp !!!
can someone please help me?
|
|
|
|
|
Is this a compile error or run error? Where are you getting the error message from?
John
|
|
|
|
|
it is a faltal error. it seams to be the run error.
|
|
|
|
|
Then a message box pops up with the error? The reason why I ask is I have seen this as a compile error and the fix was to do a clean build by deleting the release and debug folders and recompile however if it is a runtime error I am not sure if this could be the problem.
John
|
|
|
|
|
I'm pretty sure he's getting a compile time error and does not understand what you're asking him.
Christian
I have drunk the cool-aid and found it wan and bitter. - Chris Maunder
|
|
|
|
|
|
You mean it compiles, runs and then you get this error ?
Christian
I have drunk the cool-aid and found it wan and bitter. - Chris Maunder
|
|
|
|
|
no no it does not RUN... it is a compiler error.
Sorry for the mistake.
|
|
|
|
|
OK - could you post the code that is causing the problem ? Can you comment any lines out of stdafx.h and cause it to compile ?
Christian
I have drunk the cool-aid and found it wan and bitter. - Chris Maunder
|
|
|
|
|
// stdafx.h : include file for standard system include files,
// or project specific include files that are used frequently, but
// are changed infrequently
#pragma once
#define WIN32_LEAN_AND_MEAN // Exclude rarely-used stuff from Windows headers
// C RunTime Header Files
#include <stdlib.h>
#include <malloc.h>
#include <memory.h>
#include <tchar.h>
// TODO: reference additional headers your program requires here
this is all the code i have in stdafx.h!!!
I have not add anything to it!!!!
This is the default file when you want to build a form.net application... and i dont undrestand the pupose of it entirlt.
|
|
|
|
|
hold on a sec
the program will not run
but in the comments it says:
fatal error C1084: cannot read CLR runtime data file c:....stdafx.obj
|
|
|
|
|
I'd do a clean and rebuild all, it's compiling the individual files but cannot read one of them for some reason.
And you should check the 'do not treat <'s as HTML tags' box below when you post anything that could be mistaken for a tag.
Christian
I have drunk the cool-aid and found it wan and bitter. - Chris Maunder
|
|
|
|
|
Thanks Christan. I dont know why it happens sometimes but I copied another sdfxa.cpp file from another project and it works fine now  ;)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
