Re: Problem Linking (win32)

On Jul 23, 3:20 pm, "Jim Carlock" <spamt...@xxxxxxxxxx> wrote:

Did you get the other file to compile and run? I'll take a
look at this later in the evening. I've got some other things
to work out right at the moment.

I have no problems assembling and linking these asm programs. I
did figure out the @commandfile piece, which helps a lot. What
I do not understand is why an error value is set upon loading
the PE file. This happens to me when I link to msvcrt.dll.
Otherwise, if I stick to only windows api functions, the error
value is set to zero upon loading the PE file.

The PE exe files run fine since the error is all ready set before
the code executes.

Is the setting of the error value a bug with the linker, a bug
with the creation of the obj file, a bug with the ms loader,
or something else? Should I clear the error value whenever
I assemble a file that links back to msvcrt.dll after a prologue?

Given that win32 PE files based on win32 coff have been out
for a while, I expect someone to have run into this problem
before. Since I do not know what is causing the error, I
feel like my code is executing under an unknown condition.

The closest BSD problem I ran into was the need for a prologue
if I am using floating point instructions on amd64.

Thanks.



.