Board index » cppbuilder » AV in ILINK32

2008-03-20 07:25:59 AM
cppbuilder98
Have been working on a large project all evening, porting it to BCB2007
(latest update), and now I get this when compiling from the IDE:
[ILINK32 Warning] Warning: Unable to perform incremental link -
performing full link...
[ILINK32 Error] Fatal: Access violation. Link terminated.
Great...
What can I do to help CG track down this problem?
Brian
 

Hi Brian,
I am afraid you cannot do anything except ranting about how unacceptable
this situation is.
Linker dying with no explanation, no error message, no logs ...
Tss tss ....
CodeGear is informed about this problem very well.
I have even sent a linkset to CodeGear - 45 MB (zipped) of objs, libs, dfms
etc. etc. It did not help. The error seems just to be too slippery.
CodeGear should give us a new version of the linker which would make a
detailed log of all its actions and produce detailed error messages and
stack trace in case of a fatal error.
But will they ????
Meanwhile, I had to switch from static to dynamic link and distribute my app
with tons of bpl libraries which is quite annoying but works (up to now).
Pavel
"Brian" < XXXX@XXXXX.COM >píse v diskusním príspevku

Hi Pavel,
I have created a high priority case with support and hope/expect they
will provide me with guidance on how to help them track down the issue.
Brian
 

{smallsort}

Il Thu, 20 Mar 2008 11:30:55 +0100, Brian < XXXX@XXXXX.COM >ha scritto:
Along with ilink32, I use even unilink. On some projects ilink32 fails, with others
projects unilink doesn't work properly, but - using the linker that works with that
design - all my projects have worked.
I know that this is a pretty ugly solution, but sometime, ilink32 can lead to showstopper
problems; so unilink can be a desiderable immediate solution, expecially if the deadlines
of your projects are approaching fast.
Hoping, however, that CodeGear can fix the linker soon...
Regards.
Giuliano
 

Even better, a brand spanking new linker designed from scratch that provides
deugging info that can be provide to CodeGear when errors are encountered
and that is 100 times faster than ILINK32.
A good percentage of our compile/link time is spent linking the projects in
our project group.
Larry Griffiths
"Giuliano" < XXXX@XXXXX.COM >wrote in
message news: XXXX@XXXXX.COM ...

Hi Brian,
Pavel
 

Il Thu, 20 Mar 2008 08:14:52 -0500, "Larry Griffiths" < XXXX@XXXXX.COM >ha scritto:
Giuliano
 

On Mar 20, 1:37 pm, "PavelS" < XXXX@XXXXX.COM >wrote:
last april, it took till june for anyone to respond and there is still
no sign of any action.
Do they mind that this bug has been around since 2003 and was being
worked (??) on then by Borland
"Owen Urkov" < XXXX@XXXXX.COM >:
chris
 

Brian wrote:
Windows has a built in feature, dump files. I don't know if it is
possible for CG to use the dump file, written by Windows to evaluate the
problem, since for tracking down the problem debugging info in MS PDB
format is needed.
But anyways they could write at least the call stack and some additional
info to track down the problem.
We have a project, which is broken for 4 years now. It's been a BCB6
project. We changed the project settings and by disabling optimizations
we could make it link for another few weeks of development. But then the
linker stopped working again. We had ported the project also to BCB 2005
and BCB 2006, but these 2 failed too. However, we haven't tried to
compile it under BCB 2007 yet.
Andre
 

after several updates to BCB2007, I find bug after bug porting my first
project.. Access violation in rtl100.bpl, access violation in ILINK32,
Assert messages popping up when I'm writing in the editor, causing the
IDE to shut down without saving.. All kinds of nice things which make
you wonder if this version was released in a rush just to get something
new out the door ... Not really comforting. At all.
Brian
 

Hi Giuliano,
Brian
 

Brian wrote:
However, it won't work with the IDE out of the box. You'll have to use an
IDE plugin such as one of the following to use it:
- TwineCompile (www.jomitech.com/twine.php)
- bcc32pch (andy.jgknet.de/cpp/index.php)
Jon
 

Brian
 

[Linker Warning] Strange debug gprocref in
'd:\components\bcb2007\lib\ztvBCB2007_rt.lib|ztvunbzip.pas'
[Linker Warning] Strange debug gprocref in
'd:\components\bcb2007\lib\acntBCB2007_R.lib|ZLibEx.pas'
[Linker Warning] Part of linked debug-info is problematick, rejected
Causes EurekaLog stack dumps to be incomplete..
Brian
 

I do not find it so bad.
It works except for the {*word*99}py linker.
And unilink never worked for me.
Pavel
"Brian" < XXXX@XXXXX.COM >píse v diskusním príspevku