Expert Texture Home Contact me About Subscribe Digipede Connect on LinkedIn rwandering on Twitter rwandering on FriendFeed

rwandering.net

The blogged wandering of Robert W. Anderson

ilasm returned -1073741819

This is a community service post.  When I come across a problem and I can’t find a solution to it on the Internet, I try to put a solution into the public record.  This one is obscure.

When running ilasm I got an exit code of -1073741819 (the fairly generic C0000005 code).  The problem turned out to be due to an incompatible PDB file in the same directory as the input files.  I experienced this running ilasm for .NET 1.1 with a pre-existing .NET 2.0 PDB file from a previous step in our build process.

To be clear: the PDB file that caused the problem had the same base name as the IL being read and assembly being generated.  It appears that ilasm reads the PDB if it already exists, but since the file is incompatible it returns an error.

The solution here was easy: just delete or move the offending PDB.

Note that if you are running ilasm indirectly through the PreEmptive Dotfuscator product, you will see an error like this:

ilasm returned -1073741819

The FAQ at PreEmptive says that this is due to a problem of path depth (i.e., running ilasm too deeply nested in folders).  That may sometimes be the case too.  I don’t know.

Tags: , , , ,

    Trackback

2 Comments »

    Brandon Siegel wrote @ March 14th, 2008 at 11:14 am

Just came across this blog post randomly as I was searching for something else. I’ll make sure we get this into our faq – thanks for doing the homework :)

–Brandon

    Robert W. Anderson wrote @ March 14th, 2008 at 12:08 pm

Thanks, Brandon.

Your comment

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>