The MASM Forum

Projects => Rarely Used Projects => GoAsm => Topic started by: chipchuck on December 15, 2017, 11:10:08 AM

Title: GoLink size limit
Post by: chipchuck on December 15, 2017, 11:10:08 AM
When my .exe reaches X64 Size: 17,920
 access is denied.

Its great for keeping the program small, but I'd rather not.

Surely this isn't a real limit, but what do I do?
Title: Re: GoLink size limit
Post by: jj2007 on December 15, 2017, 11:31:06 AM
That's pretty odd indeed. Can you delete the exe manually? Do you see it in task manager, and can you kill it?
Title: Re: GoLink size limit
Post by: chipchuck on December 15, 2017, 11:39:31 AM
I have had to delete .exe in task manager, but not this time.

Sometimes Windows butts in with: cannot run app on this pc.

Shrinking program size always cures it.
Title: Re: GoLink size limit
Post by: wjr on December 15, 2017, 01:08:12 PM
GoLink has upper limits nowhere near that small value, so something else is going wrong.

Are you using the latest versions of the GoTools? Using GoAsm too, or just GoLink with OBJ files from another assembler/compiler? Once shrunk and cured, what do you trying adding that throws it off around that size, just data?
Title: Re: GoLink size limit
Post by: chipchuck on December 16, 2017, 03:23:15 AM
I'm using GoAsm and the latest GoLink. No OBJ files.

After shrinking I add more code till I again hit the limit. Then move more (obsolete?) code to an archive file.

This is a longstanding problem for which I haven't been able to find a solution.
Title: Re: GoLink size limit
Post by: chipchuck on December 22, 2017, 02:22:00 AM
GoLink is not the problem.

When program size reaches 17,920, Avast antivirus detects Evo-gen and sequesters the .exe file. Presumably Windows defender does the same, without a message.

The workaround is simple: increase program size 512 bytes above 18,432. Avast no longer triggers and the program runs normally.

Thanks to Wayne for his help.
Title: Re: GoLink size limit
Post by: jj2007 on December 22, 2017, 04:48:27 AM
There is a dedicated sub-forum for your problem (http://masm32.com/board/index.php?board=23.0); these guys should be thrown in quarantine for some months, so that they learn how to avoid false positives in their s**tware ;)

No option to exclude specific folders such as \Masm32 from scanning?