Would this dll call work?

[killaz219]

I'm new to DLLCALLs because I have never had a use for them before. I made this test with one of the few calls I knew, can anyone tell me if it works?

DllOpen("Kernel32.dll")
While 1
    If DllCall("Kernel32.dll", "int", "IsDebuggerPresent") = 1 then ExitLoop
    If @error then ExitLoop
    Sleep(1)
WEnd
DllClose("Kernel32.dll")

[/dev/null]

I'm new to DLLCALLs because I have never had a use for them before. I made this test with one of the few calls I knew, can anyone tell me if it works?

DllOpen("Kernel32.dll")
While 1
    If DllCall("Kernel32.dll", "int", "IsDebuggerPresent") = 1 then ExitLoop
    If @error then ExitLoop
    Sleep(1)
WEnd
DllClose("Kernel32.dll")

should work (exept for the DllOpen/DllClose part). See: http://msdn.microsoft.com/library/default....ggerpresent.asp

You should read the help file section for DllOpen(). That function returns a handle, which can be used by DllCall() and must be used by DllClose().

Cheers

Kurt

[killaz219]

should work (exept for the DllOpen/DllClose part). See: http://msdn.microsoft.com/library/default....ggerpresent.asp

You should read the help file section for DllOpen(). That function returns a handle, which can be used by DllCall() and must be used by DllClose().

Cheers

Kurt

Thanks didnt notice that

[MSLx Fanboy]

DLLCall returns an array, where [0] is the return value of the function call

[/dev/null]

DLLCall returns an array, where [0] is the return value of the function call

Ups, I overlooked that. You're of course right !!

Cheers

Kurt

[GaryFrost]

If the current process is running in the context of a debugger, the return value is nonzero.

If the current process is not running in the context of a debugger, the return value is zero.

[/dev/null]

If the current process is running in the context of a debugger, the return value is nonzero.

If the current process is not running in the context of a debugger, the return value is zero.

argh.... I need some sleep ....

@killaz219: You can only test if the return value is nonzero, as you cannot expect it to be 1 (see first statement above).

Cheers

Kurt

[killaz219]

So it would be this right?

$dll = DllOpen("Kernel32.dll")
While 1
    $dll2 = DllCall($dll, "int", "IsDebuggerPresent")
    If @error then ExitLoop
    If $dll2[0] <> 0 Then ExitLoop
    Sleep(1)
WEnd
DllClose($dll)

Edited October 24, 2005 by killaz219

[GaryFrost]

should be correct but only if:

The IsDebuggerPresent function determines whether the calling process is being debugged by a user-mode debugger.

[/dev/null]

So it would be this right?

If @error then ExitLoop

actually your error handling is not O.K. You treat a general DllCall error (@error is set) in the same way as if your program is beeing debugged. I guess that could cause problems...

EDIT: And the sleep() could be a bit longer ...

Cheers

Kurt

Edited October 24, 2005 by /dev/null

[Richard Robertson]

Wow, confusing. Why do you want to see if AutoIt is being debugged? Or was that just an example/test?

[killaz219]

Wow, confusing. Why do you want to see if AutoIt is being debugged? Or was that just an example/test?

Just a test

[GaryFrost]

actually your error handling is not O.K. You treat a general DllCall error (@error is set) in the same way as if your program is beeing debugged. I guess that could cause problems...

Cheers

Kurt

Yep, getting late, @error should only be set if the dllcall failed, if that doesn't fail then you need to check your return value.

[LxP]

When you're only performing a single DLLCall() on any DLL, you don't need to open and close it. You can have this done automatically during the call and can therefore use:

Local $Ret = DLLCall('Kernel32.dll', 'Int', 'IsDebuggerPresent')

instead of:

Local $DLL = DLLOpen('Kernel32.dll')
Local $Ret = DLLCall($DLL, 'Int', 'IsDebuggerPresent')
DLLClose($DLL)

[killaz219]

When you're only performing a single DLLCall() on any DLL, you don't need to open and close it. You can have this done automatically during the call and can therefore use:

Local $Ret = DLLCall('Kernel32.dll', 'Int', 'IsDebuggerPresent')

instead of:

Local $DLL = DLLOpen('Kernel32.dll')
Local $Ret = DLLCall($DLL, 'Int', 'IsDebuggerPresent')
DLLClose($DLL)

But I had the call in a loop, wouldn't it have to keep opening and closing it after every call if I didn't use DllOpen and DllClose?

[MSLx Fanboy]

If you're using it in a loop, that is the way to do it (or if you're calling multiple functions from the same DLL).

Local $DLL = DLLOpen('Kernel32.dll'), $Ret
Do
     $Ret = DLLCall($DLL, 'Int', 'IsDebuggerPresent')
Until $Ret[0];Do...Until there is something in $Ret[0]
 ;Until Not $Ret[0];Do...Until $Ret[0] = 0
DLLClose($DLL)

Edited October 24, 2005 by MSLx Fanboy