The MASM Forum

64 bit assembler => 64 Bit Assembler => Topic started by: TouEnMasm on August 13, 2021, 06:29:36 PM

Title: Jwasm limitations
Post by: TouEnMasm on August 13, 2021, 06:29:36 PM
Hello,
JWASM allow to debug  source code in 32 bits(more than 10 lines) in source mode(following the source) without problems,he is the only one to do that.
But ... he don't accept record in 64 bits  and don't accept long chain of constants like those ones in the attachments.
The problem is put in a comment ,delet it and link say the object file is corrupted.(win 10,VS2019 linker).


Title: Re: Jwasm limitations
Post by: Vortex on August 13, 2021, 06:56:28 PM
Hi ToutEnMasm,

The latest release of Jwasm is available from :

https://github.com/Baron-von-Riedesel/JWasm
Title: Re: Jwasm limitations
Post by: _japheth on August 13, 2021, 09:41:50 PM

Of course, a "bad" object file should *never* be created - will look into it ASAP.

A side note: bug reports for jwasm should be done in github directly.
Title: Re: Jwasm limitations
Post by: _japheth on August 24, 2021, 10:07:48 PM

The error was actually a buffer overflow, due to text macro expansion creating a line that exceeded the max line length (of 600).

At github, there's a v2.15 jwasm prerelease now: https://github.com/Baron-von-Riedesel/JWasm/releases/tag/v2.15pre1 (https://github.com/Baron-von-Riedesel/JWasm/releases/tag/v2.15pre1)

The "bad object" (or crash) error shouldn't happen anymore, but of course jwasm does now emit error "line too long".

Title: Re: Jwasm limitations
Post by: caballero on August 24, 2021, 10:57:49 PM
Good to see that jwasm is still updated  :thumbsup:
Title: Re: Jwasm limitations
Post by: TouEnMasm on August 24, 2021, 11:33:36 PM
Me also  :thumbsup: