Comment 8 for bug 9917

Message-ID: <20041205185956.GA30258@seventeen>
Date: Sun, 5 Dec 2004 19:59:56 +0100
From: Bill Allombert <email address hidden>
To: <email address hidden>
Cc: wim delvaux <email address hidden>
Subject: Re: Bug#279722: libc6: application sometimes crashes, valgrind shows error in gconv_db.c

On Sat, Nov 06, 2004 at 12:43:36PM -0500, Daniel Jacobowitz wrote:
> "Invalid read" is not a memory leak - this says something has been
> freed and then used. It looks like the destructors are running in the
> wrong order, maybe.
>
> We'd still need a testcase.

A somewhat crappy testcase:
$ apt-get install pari-gp
$ valgrind gp
\q
==30297== ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 33 from 1)

If you run instead

$ valgrind --run-libc-freeres=no gp
\q
==30314== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 33 from
1)

If you enter ^D instead of \q you do not get errors, so it might be
linked to the libc I/O subsystem.
(GP is a CLI using GNU readline.)

Of course I did not rule out a bug in the gp binary itself, but I
suppose the submitter observed the problem in an unrelated program.

Cheers,
--
Bill. <email address hidden>

Imagine a large red swirl here.