Closed gfarm-admin closed 5 years ago
Original comment by: n-soda
add some more symptoms, which are not related to libpq, to the description
Original comment by: n-soda
typo in the summary field
Original comment by: n-soda
tatebe@-san pointed out that this is a bug of glibc.
update the description field about the glibc bug.
Original comment by: n-soda
clearify about the test program and the state of RHEL5/CentOS 5
Original comment by: n-soda
The following part was incorrect (I looked at wrong source, glibc-2.5 official one, instead of Red Hat 5 source RPM), thus removed the sentence from the description:
It seems glibc in Red Hat Enterprise 5 and CentOS 5 already includes the relevant fix,
but running the test program in the bugzilla #10282 under gdb still triggers this symptom.
Original comment by: n-soda
The test script in #66 with "export MALLOCCHECK=3",
the following symptoms of invaild free() are detected:
The Cause
This is a bug of glibc:
http://sourceware.org/bugzilla/show_bug.cgi?id=10282
(pointed out by tatebe@-san)
Running the test program in the bugzilla #10282 under gdb easily triggers this symptom even without using Gfarm.
The Countermeasure
This is fixed in glibc-current as follows:
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cc49a5a8837be1f9307b167d9bf4399798a847c9
Not setting the MALLOCCHECK environment variable can workaround this problem.
Thus, ${MALLOCCHECK} shouldn't be set until glibc is fixed.
(pointed out by tatebe@-san)
Reported by: n-soda
Original Ticket: gfarm/tickets/67