DialogBoxParam causes excessive CPU usage??

[jj2007]

I bet you access a wrong memory address. Maybe you should replace the "[variable]" with "variable".

See replies #12 and #14 ("Btw..").

[MichaelW]

Using OllyDbg I've found that the program never exits from this line (it gets stuck between kernel32 and ntdll if I use Animate Trace):

Code Select Expand


invoke DialogBoxParam,[hInstance],IDD_DLG1,0,ADDR DlgProc,0


DialogBoxParam, like the other functions that create modal dialogs, does not return until the dialog is destroyed.

[Shooter]

DialogBoxParam, like the other functions that create modal dialogs, does not return until the dialog is destroyed.

Oh, that makes sense. Thanks.

I still haven't figured out why when I launch it from within RadASM the CPU usage is so high, and the dialog box never appears; yet from Windows Explorer it launches just fine. Strange. I wonder if it changed RadASM somehow.

-Shooter