[Uwe Moeller <umr@interlogic.de>] libc/2215: mcheck(): free() reports "invalid pointer" while pointer looks ok

[Uwe Moeller <umr@interlogic.de>] libc/2215: mcheck(): free() reports "invalid pointer" while pointer looks ok

[Andreas Jaeger]

We received the appended bug report.  Wolfram, can you take a look, please?

Is mcheck together with MALLOC_CHECK_=1 forbidden?  Or where is the
problem?

Andreas

Re: [Uwe Moeller <umr@interlogic.de>] libc/2215: mcheck(): free() reports "invalid pointer" while pointer looks ok

[Ulrich Drepper]

Andreas Jaeger <aj@suse.de> writes:

> We received the appended bug report.  Wolfram, can you take a look, please?
> 
> Is mcheck together with MALLOC_CHECK_=1 forbidden?  Or where is the
> problem?

I've a change for this which I'm testing in this moment.  The problem
is that the hooks are overwritten before malloc had the chance to
install it's own wrappers.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

Re: [Uwe Moeller <umr@interlogic.de>] libc/2215: mcheck(): free() reports "invalid pointer" while pointer looks ok

[Wolfram Gloger]

Hello,

> I've a change for this which I'm testing in this moment.  The problem
> is that the hooks are overwritten before malloc had the chance to
> install it's own wrappers.

OK thanks -- I think one set of hooks should take precedence, if the
hooks have already been set by mcheck then MALLOC_CHECK_ shouldn't try
to re-set them.

Regards,
Wolfram.

Which branch in CVS will become glibc-2.2.3?

[Steven J. Hill]

Greetings.

As I am actively trying to help maintain the toolchain for
Linux/MIPS, I would like to know which branch in the glibc
CVS will become the new 2.2.3 version? My guess is it will
come from one of these 3 branches:

   HEAD
   MAIN
   glibc-2_2_2

MAIN is my first guess and glibc-2_2_2 is my second guess. I
want to be able to actively test what is going to be the next
release. Thanks.

-Steve

-- 
 Steven J. Hill - Embedded SW Engineer
 Public Key: ' http://www.cotw.com/pubkey.txt '
 FPR1: E124 6E1C AF8E 7802 A815
 FPR2: 7D72 829C 3386 4C4A E17D

Re: Which branch in CVS will become glibc-2.2.3?

[Andreas Jaeger]

"Steven J. Hill" <sjhill@cotw.com> writes:

> Greetings.
> 
> As I am actively trying to help maintain the toolchain for
> Linux/MIPS, I would like to know which branch in the glibc
> CVS will become the new 2.2.3 version? My guess is it will
> come from one of these 3 branches:

We do not work on any branch at the momement.

> 
>    HEAD
>    MAIN

HEAD=MAIN=current development branch

>    glibc-2_2_2

That's no branch, that's just a release tag.
> 
> MAIN is my first guess and glibc-2_2_2 is my second guess. I
> want to be able to actively test what is going to be the next
> release. Thanks.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj