This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
Re: [Fwd: [zebra 982] Re: OSPFd coredump (glibc2.1 related?)]
- To: Florin Andrei <florin@expert.ro>
- Subject: Re: [Fwd: [zebra 982] Re: OSPFd coredump (glibc2.1 related?)]
- From: Andreas Jaeger <aj@arthur.rhein-neckar.de>
- Date: 20 Jul 1999 18:26:09 +0200
- Cc: glibc-linux@ricardo.ecn.wfu.edu
- References: <37948F82.DF45FAC1@expert.ro>
- Reply-To: glibc-linux@ricardo.ecn.wfu.edu
The description you give sounds like a classical error: Writing beyond
the memory that has been allocated. If even lefence complains, you
should investigate why it complains.
All known cases where glibc segfaults in chunk_alloc come from
corruption of the internal data structures of malloc. Run the binary
with MALLOC_CHECK_ set to 1 or 2 in the environment and see what
happens.
Andreas
--
Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de