Re: Problem Linking (win32)
- From: "bwaichu@xxxxxxxxx" <spamtrap@xxxxxxxxxx>
- Date: Fri, 25 Jul 2008 10:45:01 -0700 (PDT)
On Jul 25, 6:29 am, Frank Kotler <spamt...@xxxxxxxxxx> wrote:
Here's another example. This example results in this error being set
upon loading:
ERROR_ENVVAR_NOT_FOUND (000000CB)
Google leads me to:
http://msdn.microsoft.com/en-us/library/ms683188(VS.85).aspx
Apparently, that would be the expected result of a failed
GetEnvironmentVariable call. We didn't call GetEnvironmentVariable - not
on purpose, anyway. Did the loader call it? Is this a "misleading"
value, that means something else in this context? How long ago might
"last error" have happened? Nasm would be looking for "NASMENV", and
probably not finding it. The linker would probably be checking
environment variables, too. I wouldn't "expect" GetLastError to persist
from one program to another, but...
And this happens every time.
... just to rule it out, does "every time" include rerunning the program
without any assembling/linking in between?
Every time I debug the program in either OllyDebug or IDA Pro I find
eax
set to that same last error. My expectations are:
1) should be set to zero since none of my code has executed
2) should change since I can do other before running the program each
time
If I use a different C function, then I receive a different error. If
I use
sprintf, I receive an error invalid handler.
Any ideas? Can you reproduce my error on your machines?
I'm just "stubborn" about Windows. When the last time to "reinstall
system" came around, I said "No, Enough!". I could easily access a
machine running Windows, but I'm trying to help MicroSoft avoid becoming
a "monopoly"... Sorry...
I run openBSD as my main os. I like Theo's vision of open. But I
also run OS X
and windows on different boxes. There is also vmware if you just want
to run an image.
MS is old news anyway. Google is the new MS. People just still like
them. And people
are just starting to get angry with Apple. Feels like a bad morning
soap opera.
Brian
.
- References:
- Problem Linking (win32)
- From: bwaichu@xxxxxxxxx
- Re: Problem Linking (win32)
- From: Frank Kotler
- Re: Problem Linking (win32)
- From: Jim Carlock
- Re: Problem Linking (win32)
- From: bwaichu@xxxxxxxxx
- Re: Problem Linking (win32)
- From: Frank Kotler
- Problem Linking (win32)
- Prev by Date: Re: Atomic operations in 32 and 64 bit platforms
- Next by Date: Disassembler questions
- Previous by thread: Re: Problem Linking (win32)
- Next by thread: Re: Problem Linking (win32)
- Index(es):
Relevant Pages
|