mwldsym2.exe: Internal linker error

[McMagnus42]

I'm trying to port a project to Symbian and instead of adding several hundreds of files to a Carbide project, I'm compiling large parts of the code as before with gcc (for the simulator) and have then tried to make both a DLL and a LIB out of that code for later linking with the Symbian OS .EXE.

This worked well up to a certain point, but when I included more and more of the code into the DLL (or LIB), the Symbian linker fails with:

mwldsym2.exe: Internal linker error (please report at <http://www.forum.nokia.com>):
mwldsym2.exe: while executing in file LinkCV5.c: 'WriteModules' (line 2087)
mwldsym2.exe: Error writing file:
mwldsym2.exe: The handle is invalid.

It doesn't seem to be a code size problem, the .LIB isn't more than ~6MB. I've tried to only add some parts of the code and stub the rest, but it's very time consuming and I fail to find any logic as to when the linker error happens.

Any suggestions?

[mpinsonneault]

Are you using Express, or have you purchased the 1.1 Professional or Developer edition?

Regards,

Matt P.

[McMagnus42]

Ah, sorry.

I was actually using a command line version of mwldsym2 (from the UIQ3 SDK) with the following version info:

Nokia Codewarrior Linker for Windows/x86.
Copyright (c) 2005, Nokia Corporation
All rights reserved.
Version 3.2.3 build 446 (Build 446)
Runtime Built: Aug 15 2005 08:08:32

However, the same thing happens with the one from Carbide Express 1.0 which is:

Nokia Codewarrior Linker for Windows/x86.
Copyright (c) 2005, Nokia Corporation
All rights reserved.
Version 3.2.3 build 451 (Build 451)
Runtime Built: Nov 14 2005 14:10:39

Regards,

Magnus

[McMagnus42]

Hi again

If you want additional bug-hunting info, here's some:

I added some -progress and -verbose to the linker options and saw that it crashed when writing the "CodeViews". Then I found a debugging option called -nocodeview and when I tried it, it didn't write the CodeViews and didn't crash.

It doesn't crash either if I don't use debugging (-g) at all so I guess an UREL build would work too.

Thanks for the reply anyway and I hope someone can fix the bug with this info. I doubt I would be able to send a code sample (short of sending you the whole project) to trigger the bug, but if you want me to try something, just ask.

[mpinsonneault]

Thanks for the info, but I don't think that's enough to go on. Would you be willing to send me your entire project? If so, please message me and I'll contact you off-list.

Regards,

Matt P.