The binary couldn't be patched, because it's currently in us

delphi package - automated exception handling

The binary couldn't be patched, because it's currently in us

Postby FredS » Wed Apr 05, 2017 4:49 pm

I am getting this in Tokyo:
Code: Select all
[madExcept Warning] PA.dpr: The binary couldn't be patched, because it's currently in use.


I am running code in the Post-Build Even as posted in: viewtopic.php?f=4&t=5531#p50765

I should add: the binary does get patched so not mission critical..
FredS
 
Posts: 79
Joined: Mon May 11, 2015 9:42 pm

Re: The binary couldn't be patched, because it's currently i

Postby madshi » Mon Apr 10, 2017 8:55 am

Do you have any idea why the EXE might be "in use"? I've no idea right now.

(This error message means that madExcept wasn't able to open the file for write access.)

Maybe your Anti-Virus software opens the file to check it and at that point madExcept tries to patch it, but can't open it for write access because the AV software is checking it?
madshi
Site Admin
 
Posts: 9470
Joined: Sun Mar 21, 2004 5:25 pm

Re: The binary couldn't be patched, because it's currently i

Postby FredS » Mon Apr 10, 2017 7:08 pm

madshi wrote:Do you have any idea why the EXE might be "in use"?


Since this all works in Berlin either you changed the timing of your call for Tokyo or Tokyo hasn't been tested well enough. My bet is on the latter.. :)
FredS
 
Posts: 79
Joined: Mon May 11, 2015 9:42 pm

Re: The binary couldn't be patched, because it's currently i

Postby madshi » Mon Apr 10, 2017 7:20 pm

Well, at least I haven't changed anything timing related... :lol:
madshi
Site Admin
 
Posts: 9470
Joined: Sun Mar 21, 2004 5:25 pm


Return to madExcept

Who is online

Users browsing this forum: No registered users and 3 guests