|
That it is a good question. I don't know if it has a version.
|
|
|
|
|
Have you looked at the date field in the PE header?
See PE Format - Win32 apps | Microsoft Docs[^]
It’s not exactly a version information but it might give you an ordering of the different versions. That’s assuming the linker used to create the app bothered to fill it. Most, but not all, do.
Mircea
|
|
|
|
|
Hi!
I try to implement a callback function within a dll, which triggers an assigned function in the main application. I want to trigger this "event" in the main app from within the dll.
Here is my code from the dll:
extern "C" __declspec(dllexport) void funcA(const unsigned long long a, const unsigned long long b);
extern "C"
{
typedef void(__stdcall* callback_t)(unsigned int halfbeast);
__declspec(dllexport) void public_func_taking_callback(callback_t evHnd)
{
evHnd(333); }
}
void funcA(
const unsigned long long a,
const unsigned long long b)
{
if(a>10) callback_t(public_func_taking_callback);
}
Here is the code I use in the main application to load the library and attach to the functions:
typedef void (__stdcall *eventCallback)(unsigned int miau);
typedef void (__stdcall *setCallback)(eventCallback evHnd);
void __stdcall CallB(unsigned int);
void __fastcall TForm1::Button1Click(TObject *Sender)
{
signed int retval;
unsigned int i;
char txt[7];
unsigned long long a,index;
UnicodeString USt;
HINSTANCE dllHandle=NULL;
dllHandle = LoadLibrary(L"test.dll");
if (!dllHandle){
ShowMessage("Could not load test.dll");
Form1->Close();
}
else{ void (__stdcall* funcA)(const unsigned long long a, const unsigned long long b);
funcA=(void(__stdcall*)(const unsigned long long a, const unsigned long long b))GetProcAddress(dllHandle,"funcA");
setCallback values=(setCallback)GetProcAddress(dllHandle, "public_func_taking_callback");
if(values != NULL){
values(&CallB);
}
if(!funcA){
Memo1->Text="No handle to function found.";
}
else{
funcA(1,1);
funcA(100,100);
}
FreeLibrary(dllHandle);
}
}
void __stdcall CallB(unsigned int halfbeast){
ShowMessage("triggered");
}
What happens is unfortunately not what I wanted:
1) In the very moment the line "values(&CallB);" is executed, CallB is called. This is not what I wanted, I justed wanted to give the callback pointer of the dll to my function CallB.
2) CallB is not called when the line "funcA(100,100);" is executed. Most likely there is something wrong with the function call within the dll, but I cannot see it...
|
|
|
|
|
1. That is correct. At that point, values is set to public_func_taking_callback , which takes the address of a function and immediately calls it.
2. funcA calls callback_t , but callback_t has never been set to any value.
To be honest, I find it difficult to understand your code, so I may have still missed something. However, you should be able to see the exact sequence of events by running the code in the debugger.
|
|
|
|
|
Hi Richard,
thanks for the answers. Yes I can debug it, but it doesn't help me much, since I don't understand why it behaves that way.
1.) OK, got it. Unfortunately then I do not know, how I pass the address of the function of CallB to the dll. I want the dll to call CallB() in the moment callback_t is called.
Most likely I confuse here something, but I find it very hard to understand the syntax. It seems even harder since it is wrong
I wasn't able to find any C++ examples for that.
2.) I thought I set it to public_func_taking_callback, but obviously this is not the case.
Maybe I should explain again, what I try to do:
In my main application I want to declare a function. This function should be registered in the dll as a callback function. When during run time in the dll some criteria match ( if(a>10) ) the dll should call the function in the main application and execute it.
|
|
|
|
|
Bodo2407 wrote: I don't understand why it behaves that way. It behaves that way because that is the way you have written the code.
1. So you need to change the code in public_func_taking_callback as follows:
__declspec(dllexport) void public_func_taking_callback(callback_t evHnd)
{
callback_t = evHnd; }
And you need to change funcA to:
if(a>10) callback_t(a);
Again, make these changes and then step through the code in the debugger to check that it is correct.
|
|
|
|
|
Hi Richard,
thanks a lot, but unfortunately it cannot compile:
__declspec(dllexport) void public_func_taking_callback(callback_t evHnd)
{
callback_t = evHnd; }
Failure given:
-Error C2513 'void (__stdcall *)(unsigned int)': no variable declared before '='
So the typedef earlier doesn't work or... ?
|
|
|
|
|
callback_t is a type, not a function.
In your DLL , you do need a variable of such a type, in order to store the user function address.
Something similar to (not tested)
typedef void (__stdcall* callback_t) (unsigned int halfbeast);
static callback_t s_user_function = nullptr;
extern "C" __declspec(dllexport) void funcA(const unsigned long long a, const unsigned long long b);
extern "C"
{
__declspec(dllexport) void public_func_taking_callback(callback_t evHnd)
{
s_user_function = evHnd; }
}
void funcA(
const unsigned long long a,
const unsigned long long b)
{
if(a>10 && s_user_function != nullptr) s_user_function(333); }
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Thanks Carlo, I missed that.
|
|
|
|
|
Thanks a lot guys! It works now!
I really appreciate your help.
Now it also makes much more sense to me.
|
|
|
|
|
As you pointed out, the OP code looked a bit confused.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
CPallini wrote: a bit confused I assumed that was just me.
|
|
|
|
|
OK, now I experience another issue with it, I'm sorry.
Hopefully you can help me here as well.
I now want to call the callback function if an timer expires. Therefore I create an timer in a function I call from the main application. I store the handles to the timer and the timer queue globally in static variables.
static HANDLE gDoneEvent;
static HANDLE hTimer = NULL;
static HANDLE hTimerQueue = NULL;
int arg = 123;
VOID CALLBACK TimerRoutine(PVOID lpParam, BOOLEAN TimerOrWaitFired)
{
if (lpParam == NULL)
{
return;
}
else
{
if(s_user_function!=nullptr)
s_user_function(12);
}
}
Now, in some function called from the main application, I allocate the timer and start it:
char timer_init(void)
{
gDoneEvent = CreateEvent(NULL, TRUE, FALSE, NULL);
if (NULL == gDoneEvent)
{
return 1;
}
hTimerQueue = CreateTimerQueue();
if (NULL == hTimerQueue)
{
return 2;
}
CreateTimerQueueTimer(&hTimer, hTimerQueue, (WAITORTIMERCALLBACK)TimerRoutine, &arg, 3000, 10000, 0);
WaitForSingleObject(gDoneEvent, INFINITE);
}
As you can see, I don't close the handles and delete the timer queue on purpose.
Everything works fine as long as the process waits. The callback in the main application is called.
If I comment out the line with WaitForSingleObject I'll get an access exception, although I stored all the handles globally. Teh exception occurs with the timing the timer would have. So most likely it tries to call the callback of the timer function but something is missing.
What is it I'm overlooking?
I need the dll running, not waiting inside a fucntion for a timer...
|
|
|
|
|
Bodo2407 wrote: I need the dll running, not waiting inside a fucntion for a timer.. I am not sure what you mean by that. When you create a timer, it is designed to call some function after a specified period of time, either once or repeatedly. The reason for having the call to WaitForSingleObject , is in case the main code needs the timer event to complete some action first. But it is not necessary if the remainder of the code does not rely on the actions of the timer event.
|
|
|
|
|
Hi Richard,
yes, I know that. I did put that in, because I got the exception and wanted to try the example code. This worked two times, so I thought it must be caused by leaving the function. Unfortunately thsi is not the case:
After some debugging runs it seems that (in rare cases) it works a few times, but most likely it crashes immediately. So the observation I made that it is working if I call WaitForSingleObject isn't correct, it can crash randomly with or without.
Unfortunately when it crashs the program pointer isn't on frame any more, so I don't see why it does that.
One observation I made is that the handle of gDoneEvent is allocated in an entirely different address room (0x000003b0) than the other two handles hTimer and hTimerQueue(0x008b8928 and 0x008bsomething) which seems strange to me, since I thought allocated event should be also pretty close to the handles, but obviously it is not.
modified 16-Apr-21 11:04am.
|
|
|
|
|
Those numbers do not mean anything, except to the operating system.
|
|
|
|
|
Problem 1 — Flawed MAC designs (11 marks) For this problem, you need to carefully trace through the given MAC algorithms, and
|
|
|
|
|
No idea what that is supposed to be. Maybe you lost connection while typing.
|
|
|
|
|
You never asked a question, but based on what other people are doing lately, it seems you're just trying to post your homework assignment from Chegg Study, thinking someone is going to write the code for you.
That's not going to happen.
|
|
|
|
|
Copy off of the guy sitting next to you. It's your only hope.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
Hi
I have a C DLL that processes data for a MFC C++ program. It happens to be my FTP folder where files are received from FTP. when I step thru the code under the VS debugger everything runs fine
I make a breakpoint in the MFC code and when after getting the ProcAddress I go into the function.
So how do I know what the problem is when I don't run under the VS debugger, well I have a SEH (handler that pops up with a messagebox and I attach the debugger and observe the rc from _sopen_s that fails)
I decided to put a MessageBox in when it fails (in the DLL) and upon entry to the DLL as well, in the hope that I can then attach the debugger and get a better idea but the messagebox fails to appear I do re-link the MFC program as well
I went as far a deleting the .lib TO ensure I was picking it up while linking the MFC program and I got a link error so I know its picking the .lib of the DLL
I am running both the (VS Debugger and the MFC program in administrator mode)
|
|
|
|
|
Well it could be any one of a million things, but without more information it is pointless trying to guess. Also deleting the .lib file does not guarantee that you are loading the correct .dll at execution time. You should start by rebuilding everything from clean to ensure that no component is out of sync. Secondly, and much more importantly, where does the EACCESS * error occur, and what is the code trying to do at that point?
*EACCESS is returned (most often) when trying to access some file/directory that is protected. And even when running in admin mode some things remain blocked.
|
|
|
|
|
The EACCESS occurs on _sopen_s the only thing I can think of regarding that is that I have the path + filename and maybe the open function only takes a file name
Regardless I’m gong you’re-build the DLL thanks
|
|
|
|
|
What exactly are you trying to open, and what sharing options are you using?
Quote: EACCES The given path is a directory, or the file is read-only, but an open-for-writing operation was attempted.
|
|
|
|
|
It’s a mainframe z/os sysadata file which is a binary representation of Z/OS Assembler program listing I have all the big endian conversion routines for going from mainframe to pc it did work as I was able to display the listing in the richedit that called the DLL and processed this file thanks
|
|
|
|