On Tue, 18 Nov 1997, Orn E. Hansen wrote:
> The reason I say, that you need to purge them (especially if you are
> doing development), is because of...
> 0x401c6230 in malloc ()
> (gdb) bt
> #0 0x401c6230 in malloc ()
> #1 0x401c6145 in malloc ()
> #2 0x401c12cc in fopen ()
> #3 0x80ab65b in getline ()
> #4 0x80abb5c in getline ()
> #5 0x80ada67 in getline ()
> #6 0x80afcb9 in getline ()
> #7 0x8051b25 in _start ()
> #8 0x805330d in _start ()
> #9 0x40038bfc in fl_object_qread ()
> #10 0x40046ef5 in fl_do_forms ()
> #11 0x80570fd in _start ()
> Programs like xfig, and ghostview will produce similar results...
> SIGSEGV in malloc() or free(). The reason here, appears to be that
> libc5 and libc6 use two different malloc routines and algorithms... and
> CAN'T be used side by side.
The problem is that linking a program with both libc6 and librarys linked
with libc5 will produce problems. Programs that are linked this way
should have bugs filed against them if they haven't been already. Yes you
need to purge and reconstruct your development environment, but it isn't
impossible or even difficult to live with both c librarys.
Scott K. Ellis <email@example.com> http://www.gate.net/~storm/
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .