64 bit assembler > UASM Assembler Development

UAsm 2.41 bug, unknown cause.

(1/4) > >>

jimg:

The following program fails in assembly

--- Code: ---.686p
.model  flat, stdcall
option  casemap :none   ; case sensitive
.xmm
.data
ProgName db "Uasm Test",0
.code
.nolist
include windows.inc

.code

Program:
    invoke ExitProcess, 0
end Program

--- End code ---

The output:

--- Code: ---UASM v2.41, Sep 29 2017, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.

***********
ASCII build
***********

F:\masm32\INCLUDE\winextra.inc(25183) : Error A2169: General Failure
 F:\masm32\INCLUDE\winextra.inc(25183): Included by
  F:\masm32\INCLUDE\windows.inc(26889): Included by
   R:\bugtest\Sol.asm(10): Main line code

--- End code ---

If I take out the .nolist, I get

--- Code: ---F:\masm32\INCLUDE\windows.inc(21253) : Error A2169: General Failure
 F:\masm32\INCLUDE\windows.inc(21253): Included by
  R:\bugtest\Sol.asm(10): Main line code

--- End code ---

So I really don't know how to pin down the error much more without stripping stuff out of windows.inc
I downloaded and installed the latest masm32v11r.zip to get windows.inc and winextra.inc to be sure mine weren't corrupted.  They were identical, so that's not the problem.


jj2007:
It fails also for me:

UAsm64, latest build of today:
Tmp_File.asm(14) : Error A2160: INVOKE requires prototype for procedure

ML 6.15:
tmp_file.asm(14) : error A2006: undefined symbol : ExitProcess

jimg:
okay-

same error with this program:

--- Code: ---.686p
.model  flat, stdcall
option  casemap:none
.code
include R:\bugtest\windows.inc
.code
Program:
    ret
end Program
--- End code ---
no more invoke.

habran:
I'll work on this later this afternoon
now I am busy with 32bit -> 64bit RECORD :dazzled:

jimg:
No problem.  I'm grateful for all you do  8)

Anyway, I just spent hours deleting stuff out of windows.inc and the problem seems to be more like it is a Uasm internal buffer problem, rather than something specific with the actual code.  "Seems"  being the operative word, I can't absolutely confirm yet.

Navigation

[0] Message Index

[#] Next page

Go to full version