This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problems linking egcs-made applications with sicstus prolog
- To: gcc at gcc dot gnu dot org, roosen at ltt dot rwth-aachen dot de
- Subject: Re: Problems linking egcs-made applications with sicstus prolog
- From: mrs at wrs dot com (Mike Stump)
- Date: Mon, 26 Jul 1999 13:54:49 -0700
> Date: Mon, 26 Jul 1999 22:24:23 +0200
> From: Peter Roosen <roosen@ltt.rwth-aachen.de>
> Due to alleged problems of the malloc() family of system libraries
> in Linux the sicstus team has re-implemented those functions, thus
> demanding the use of SP_malloc(), SP_free() etc in our programs
> instead of the original ones.
This is the wrong solution. The right solution is to ensure that
malloc is the real cause, and if it is, to help fix the problem you
perceive in malloc. You need to work with the maintainers of the GNU C
library.
If the problem isn't in malloc, then you need to find a way to use it
that suites your application.
But I am sure you knew all of this...
> Our question now: if we overload the malloc() family with the SP_
> routines - will the C++ operators "new" and "delete" use them, too?
> If yes, this would be a very simple and elegant way to overcome
> those rather nasty problems.
I expect this should mostly work.