BorlandTalk.com

chris · Guest

Okay, maybe "solved" is too optimistic, but I wanted people to read
this post in case it helps. I have been working with Borland C++
Builder 6 for 3-4 years. In porting a large Linux program to Windows,
from the very beginning I would get an error saying:

Linker Error: Fatal Access Violation

For years I worked around the problem by restarting the IDE, which
often made the problem go away. Recently, I moved to a new machine
where I encountered the same linker problem, only this time I couldn't
make it go away by restarting the IDE, no matter how many times I
tried. Following the advice of someone who posted on this same issue,
I gradually dismantled my program until I found the offending line.
The problem seems to be a rather large array that was *declared*
rather than allocated at run time. I am never sure if I am using this
term correctly, but what I mean is that my program had

float xxx[LARGE_NUMBER];

rather than

float *xxx;
xxx = malloc(sizeof(float)*LARGE_NUMBER);

I do not know why this should cause such a problem, but have observed
problems with large arrays on several platforms. Though, this is no
excuse for Borland, since the c compliler and linker were their "bread
and butter" for years and they absolutely should be able to diagnose
and fix a problem like this given the many many posts and complaints
they have received. If you folks at Borland are listening (and I
doubt this) you totally dropped the ball here.

Hope this helps.

Chris