![]() |
|
|
|
#1
|
||||
|
||||
|
Hello:
If you disassemble the code of your a.exe, you could see imports (with wdasm32, for instance) and there all the apis used by the application. Then, select in the import window "ExitProcess" and display it, then you are getting a "call [<address of ExitProcess>]". You could write down in your new code a call like that you have got, or a jmp to the RVA of that call. Cheers Nacho_dj |
|
#2
|
||||
|
||||
|
you don't need an API.
MOV EAX,101 PUSH 0 (exit code) PUSH -1 MOV EDX,ESP INT 2E code directly converted in short form from Debug Me 0.2 / Teerayoot
|
|
#3
|
|||
|
|||
|
Quote:
Interrupts are platform dependent and using call to ExitProcess is much more versatelite. Interrupts are good to avoiding fast detection 'cause I look first for some API call or SEH usage but not for INT's. |
|
#4
|
||||
|
||||
|
yeah, i forgot to mention this only works on NT-based systems. Windows ME for example will show you the blue screen of death
also a way to get the application to shutdown, but not very nice
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| APIs in Olly | jump | General Discussion | 3 | 09-25-2013 19:03 |
| help patching apis | Shub-Nigurrath | General Discussion | 7 | 01-26-2006 17:16 |