- Welcome to The MASM Forum.
News:
Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change
Recent posts
#1
Windows API / Re: DLL pickle
Last post by NoCforMe - Today at 05:44:14 AMHere's the structure of my program that uses the DLL:
You cannot view this attachment.
The DLL is a debugger (data-only logger, no code or CPU, but still very useful) that's called on demand from the debugee.
The watch facility is one of many possible functions. When the debugee calls for a variable to be watched, it sends a watch request to the DLL.
If this is the first watch request it has to set up the watch window. That's when it calls the initialization code for the mcLB2 (multi-column listbox) control used in the watch window, which includes registering the class for that control. The DLL then creates the watch window with the mcLB2 control in it.
The DLL also has a main UI window. If this window is closed by the user, the DLL remains loaded.
So I'm curious about how exactly processes work here. Does the DLL run in a separate process, or is it part of the debugee's process? Also, my understanding is that the DLL will be unloaded when the last program (process) that uses it terminates (i.e., when the reference count goes to zero); is that correct? It seems to work that way.
In any case, everything seems to be working OK. One possible snag occurs to me, though: what if there are multiple programs that are using that control? That means that the class will remain registered even after the DLL is unloaded.
So much to keep track of here ...
You cannot view this attachment.
The DLL is a debugger (data-only logger, no code or CPU, but still very useful) that's called on demand from the debugee.
The watch facility is one of many possible functions. When the debugee calls for a variable to be watched, it sends a watch request to the DLL.
If this is the first watch request it has to set up the watch window. That's when it calls the initialization code for the mcLB2 (multi-column listbox) control used in the watch window, which includes registering the class for that control. The DLL then creates the watch window with the mcLB2 control in it.
The DLL also has a main UI window. If this window is closed by the user, the DLL remains loaded.
So I'm curious about how exactly processes work here. Does the DLL run in a separate process, or is it part of the debugee's process? Also, my understanding is that the DLL will be unloaded when the last program (process) that uses it terminates (i.e., when the reference count goes to zero); is that correct? It seems to work that way.
In any case, everything seems to be working OK. One possible snag occurs to me, though: what if there are multiple programs that are using that control? That means that the class will remain registered even after the DLL is unloaded.
So much to keep track of here ...
#2
Windows API / Re: DLL pickle
Last post by sinsi - May 12, 2025, 07:29:16 PMAfter reading more, it seems that there are two times you would need to use UnregisterClass
- if you are registering with CS_GLOBALCLASS
- this means that the DLL has to be in memory in case another process is using your class
- Raymond mentions a registry key to ensure your DLL is loaded by every process, but I'm not sure that works anymore
- if you are dynamically loading/unloading your DLL
- if you are then you control the register/unregister calls
The main point from Raymond is (I think)
- if you are registering with CS_GLOBALCLASS
- this means that the DLL has to be in memory in case another process is using your class
- Raymond mentions a registry key to ensure your DLL is loaded by every process, but I'm not sure that works anymore
- if you are dynamically loading/unloading your DLL
- if you are then you control the register/unregister calls
The main point from Raymond is (I think)
QuoteUnregister your classes if the process is going to continue running after your DLL unloads.
#3
Windows API / Re: DLL pickle
Last post by NoCforMe - May 12, 2025, 07:27:31 PMWellll, apparently my problem kind of solved itself.
Not really: I made some changes to my program. But it looks as if when the DLL is unloaded, the registered class gets automagically un-registered, probably because it's being created by the process that loaded the DLL and not the DLL itself.
This is all very confusing, but the Raymond Chen stuff you linked to, sinsi, is helpful.
One thing I found is that in order to make the whole thing work, in my DLLMain() proc, I had to use GetModuleHandle(NULL) instead of using the instance handle that's the 1st parameter of that function. This retrieves the instance handle of the calling process, not of the DLL.
So apparently no need to use UnregisterClass().
BTW, in searching for info online I found an interesting discussion of this issue on a board called Cprogramming.com, including a couple posts by our own @adeyblue, from 10 years ago.
Oh, and I'm not using CS_GLOBALCLASS, as this is a private class only used by the DLL itself.
Not really: I made some changes to my program. But it looks as if when the DLL is unloaded, the registered class gets automagically un-registered, probably because it's being created by the process that loaded the DLL and not the DLL itself.
This is all very confusing, but the Raymond Chen stuff you linked to, sinsi, is helpful.
One thing I found is that in order to make the whole thing work, in my DLLMain() proc, I had to use GetModuleHandle(NULL) instead of using the instance handle that's the 1st parameter of that function. This retrieves the instance handle of the calling process, not of the DLL.
So apparently no need to use UnregisterClass().
BTW, in searching for info online I found an interesting discussion of this issue on a board called Cprogramming.com, including a couple posts by our own @adeyblue, from 10 years ago.
Oh, and I'm not using CS_GLOBALCLASS, as this is a private class only used by the DLL itself.
#4
UASM Assembler Development / Re: Riemann Zeta Function
Last post by six_L - May 12, 2025, 06:55:52 PMHi,TimoVJL/jack
Thanks for sharing.
Here have the Zeta(z) 7 Nontrivial zeros.
Thanks for sharing.
Here have the Zeta(z) 7 Nontrivial zeros.
#5
Windows API / Re: DLL pickle
Last post by TimoVJL - May 12, 2025, 05:29:21 PMIf component DLL have safeguard mechanism, it deny to unload as long there are a windows using it.
FindWindow can find windows by registered class.
Perhaps some component code show, how they work.
Dynamic-Link Library Best Practices
What is the HINSTANCE passed to CreateWindow and RegisterClass used for?
FindWindow can find windows by registered class.
Perhaps some component code show, how they work.
Dynamic-Link Library Best Practices
What is the HINSTANCE passed to CreateWindow and RegisterClass used for?
#6
Windows API / Re: DLL pickle
Last post by sinsi - May 12, 2025, 01:07:21 PMDon't forget to unregister your window classes when your DLL shuts down dynamically
This talks about CS_GLOBALCLASS, are you using that flag?
This talks about CS_GLOBALCLASS, are you using that flag?
#7
Windows API / Re: DLL pickle
Last post by NoCforMe - May 12, 2025, 12:34:27 PMNo; I'm calling an initialization function in another module (linked into the DLL) which calls RegisterClassEx(). No export.
Now I'm confused: let's say I did have a DLL export, "UnregisterMyClass()". Would the application that's using the DLL have to call that function? And how would it know when the proper time to do that is? Keep in kind that all windows of that class have to be destroyed before you can unregister the class.
No, I don't think that would work.
I've found some stuff online that may be of help, will post more later after I digest it.
Now I'm confused: let's say I did have a DLL export, "UnregisterMyClass()". Would the application that's using the DLL have to call that function? And how would it know when the proper time to do that is? Keep in kind that all windows of that class have to be destroyed before you can unregister the class.
No, I don't think that would work.
I've found some stuff online that may be of help, will post more later after I digest it.
#8
Windows API / Re: DLL pickle
Last post by sinsi - May 12, 2025, 12:29:21 PMDo you have a DLL export to register your classes? Then you should also have a DLL export to unregister them I guess.
#9
Windows API / DLL pickle
Last post by NoCforMe - May 12, 2025, 09:40:12 AMI'm in a pickle with a DLL.
The DLL registers a window class, in a different .obj module linked with the main DLL code.
Problem is, I just discovered that window classes registered by a DLL are not automatically unregistered when the DLL is unloaded (as they are when an application terminates). From the documentation for RegisterClassEx():
OK, so I need to unregister that class manually.
But that's a problem: I can't do it in the DLLMain() entry point, because of the restrictions on what you can do there:
UnregisterClass() is in User32.dll.
So how do I do this? I need to unregister when the DLL reason is DLL_PROCESS_DETACH. But I can't do it in the DLLmain() function.
I thought of sending a message somewhere else that could do this, but SendMessage() is also in User32.dll.
The DLL registers a window class, in a different .obj module linked with the main DLL code.
Problem is, I just discovered that window classes registered by a DLL are not automatically unregistered when the DLL is unloaded (as they are when an application terminates). From the documentation for RegisterClassEx():
QuoteNo window classes registered by a DLL are unregistered when the DLL is unloaded. A DLL must explicitly unregister its classes when it is unloaded.
OK, so I need to unregister that class manually.
But that's a problem: I can't do it in the DLLMain() entry point, because of the restrictions on what you can do there:
QuoteYou should never perform the following tasks from within DllMain:
- Call functions in User32.dll or Gdi32.dll. Some functions load another DLL, which may not be initialized.
UnregisterClass() is in User32.dll.
So how do I do this? I need to unregister when the DLL reason is DLL_PROCESS_DETACH. But I can't do it in the DLLmain() function.
I thought of sending a message somewhere else that could do this, but SendMessage() is also in User32.dll.
#10
UASM Assembler Development / Re: Riemann Zeta Function
Last post by jack - May 12, 2025, 08:17:24 AMI updated my FreeBasic code
the Riemann zeta function now supports both negative and complex arguments
there's a bug in there somewhere, zeta(-20.1) gives the wrong sign, other than that the value is ok
the complex cosine is giving the wrong sign, any trig experts here?
fixed
sample output
the Riemann zeta function now supports both negative and complex arguments
the complex cosine is giving the wrong sign, any trig experts here?
fixed
sample output
Code Select
Dim As complex x, y, z
Dim As Double rr, ri
for rr=-1 to 1 step .5
for ri=-1 to 1 step .5
x=complex(rr, ri)
y=zeta(x)
print using "zeta(##.####, ##.####) = ";x.re;x.im;
print using "##.################, ##.################";y.re;y.im
next
next
zeta(-1.0000, -1.0000) = 0.0168761517881836, 0.1141564804323963
zeta(-1.0000, -0.5000) = -0.0538894302820935, 0.0752004260118382
zeta(-1.0000, 0.0000) = -0.0833333333333334, 0.0000000000000000
zeta(-1.0000, 0.5000) = -0.0538894302820935, -0.0752004260118382
zeta(-1.0000, 1.0000) = 0.0168761517881836, -0.1141564804323963
zeta(-0.5000, -1.0000) = -0.0008178931340101, 0.2230716886972805
zeta(-0.5000, -0.5000) = -0.1407574606243030, 0.1580763818474494
zeta(-0.5000, 0.0000) = -0.2078862249773547, 0.0000000000000000
zeta(-0.5000, 0.5000) = -0.1407574606243030, -0.1580763818474494
zeta(-0.5000, 1.0000) = -0.0008178931340101, -0.2230716886972805
zeta( 0.0000, -1.0000) = 0.0033002236853245, 0.4181554491413226
zeta( 0.0000, -0.5000) = -0.2991978789224703, 0.3593711792648014
zeta( 0.0000, 0.0000) = -0.4999999999999991, 0.0000000000000000
zeta( 0.0000, 0.5000) = -0.2991978789224703, -0.3593711792648014
zeta( 0.0000, 1.0000) = 0.0033002236853245, -0.4181554491413226
zeta( 0.5000, -1.0000) = 0.1439364270771889, 0.7220997435316735
zeta( 0.5000, -0.5000) = -0.4593028903460181, 0.9612542845058791
zeta( 0.5000, 0.0000) = -1.4603545088095850, 0.0000000000000000
zeta( 0.5000, 0.5000) = -0.4593028903460181, -0.9612542845058791
zeta( 0.5000, 1.0000) = 0.1439364270771889, -0.7220997435316735
zeta( 1.0000, -1.0000) = 0.5821580597520036, 0.9268485643308069
zeta( 1.0000, -0.5000) = 0.5784330210993112, 1.9635494964529780
zeta( 1.0000, 0.0000) = -1.#IND000000000000, -1.#IND000000000000
zeta( 1.0000, 0.5000) = 0.5784330210993112, -1.9635494964529780
zeta( 1.0000, 1.0000) = 0.5821580597520036, -0.9268485643308069