incremental liner

Iam using a third party vendor shared library.I am observing that my executable crahes if I use the debug version and it works fine with the release version.

Same observation is there when I turn off the incremental linker which makes the code to run fine. If it is on I get a core dump.

Can there be a logical reason to this?

[345 byte] By [linker] at [2007-11-26 9:06:47]
# 1
OS Solaris 8Using Sun workshop compilers 4.2My code is a C++ code whereas the vendors is a C lib
linker at 2007-7-6 23:20:44 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 2
As for incremental linking, it can be that some of the code that makes into the executable is new and some is old. I see the same thing with my own code sometimes.
MaximKartashev at 2007-7-6 23:20:44 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 3
Maxim,Can you please elaborate on that more. I did not get you completely.Because in both the builds(debug) and release , I do a clean build
linker at 2007-7-6 23:20:44 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 4
Ah... If you do a clean build, this indeed is strange. Clean build always helps me with the problems I am experiencing.
MaximKartashev at 2007-7-6 23:20:44 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 5

> OS Solaris 8

> Using Sun workshop compilers 4.2

Sun workshop 4.2 is not expected to work on Solaris 8, and is not supported at all.

Please upgrade to the current release, Sun Studio 11, which is free. You can get it here:

http://developers.sun.com/prodtech/cc/index.jsp

The C++ MIgration Guide explains how to migrate from C++ 4.2 to current compilers. The current compilers have an option to emulate C++ 4.2.

clamage45 at 2007-7-6 23:20:44 > top of Java-index,Development Tools,Solaris and Linux Development Tools...