On Thu, Dec 2, 2010 at 5:58 PM, Geir Meyer <Geir.Meyer@...> wrote:
>> Any ideas what else could be responsible for the problem?
> Sorry, no, but since it is ld.exe that hangs, should it not be possible to build a debug version of ld.exe from source,
> and see what really happens by using gdb ?
Yes, it is possible. As I have to start developing for my project,
initially I will link in XP in VMware. After few days I will have some
time and I will investigate this issue further.
I'm willing to help, which means compiling ld.exe with debug
information and tracing the difference in execution on my computer and
the computer of my friend (where it linked just okay).
I will need some help from you, since I don't really understand
ld.exe's internals, but at least I will point the function or code
chunk where the problems happens.
On Thu, Dec 2, 2010 at 6:59 PM, J Decker <d3ck0r@...> wrote:
> watcom demands that you compile with the correct build target type
> flags - like -bd or -bw otherwise it doesn't work right at all...
I spent so much time with this linker and I had so many issues, that
I'm not willing to continue trying. However, thanks for pointing out
that it can be used to link GCC generated code. I wasn't aware,
because I never used anything else than ld.
> System memory issue? Run the CMOS memory diagnostics to find out.
Tonight I will leave memtest86+ to test my system memory, but this
seems very, very unlikely. I don't remember having an OS crash for
months and I don't restart the OS for weeks. If I had any memory
problems, I would have noticed. However, I will surely run memtest86+.
Also the same linking problem occurs on my friend's machine using my
Windows 7 32 bit VMware image, so my hardware is ruled out.