Error when compiling

[NewsArchive]

I've been getting the attached message multiple times since yesterday. Any
idea why?

Abe Jimenez

[NewsArchive]

Abe,

> I've been getting the attached message multiple times since yesterday.
> Any idea why?

No, sorry. No idea. Seems to be something on your machine that changed.
Perhaps a "bad" virus definition update or a "protection" software update,
etc.

Friedrich

[NewsArchive]

Friedrich,

It always seems to happen when it's adding the digital certificate
(signtool.exe).

Abe

[NewsArchive]

Abe,

> It always seems to happen when it's adding the digital certificate
> (signtool.exe).

I would suggest to check the code-signing certificate expiration date.
Signtool.exe seems to corrupt the stack and brings the IDE down. And try to
see if "disabling" timestamp helps (perhaps the updated protection software
monitors signtool.exe, causes a silent crash in it which then corrupts the
stack). If it happens when Microsoft code-signing is done then chances are
that it's caused by an update in your protection software or definition
file. What you can try is to add signtool.exe and sb7.exe to your "exclude"
list to see if this can help to work around the protection software issue.

BTW, signtool.exe requires dependency components on Windows 7+ (e.g.
capicom). Perhaps "something" removed/updated these dependency files and
this causes the crash.

Friedrich

[NewsArchive]

Friedrich,

The funny thing is that sometimes it works. My code signing certificate is
not expired. See image.

Regards,
Abe

[NewsArchive]

Abe,

> The funny thing is that sometimes it works. My code signing certificate
> is
> not expired. See image.

Yes, that's typical for a bug in the "protection" software (or a bad
definition update). The security software real-time monitors signtool.exe
because it modifies the binary contents of a file - this monitoring process
seems to crash the Microsoft Authenticode tool in your case.

You said that you have been getting the error multiple times since
yesterday. So I think it's caused by one of your latest security software
and/or definition updates.

Friedrich

[NewsArchive]

I switched the timestamp url from comodo to verisign and it seems to have
fixed the problem. At least I have not had any errors in the last 4
compiles.

Abe Jimenez

[NewsArchive]

> I switched the timestamp url from comodo to verisign and it seems to
> have fixed the problem. At least I have not had any errors in the
> last 4 compiles.

Interesting! In theory, this should not make a difference.

Friedrich