This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA]: Fix gdb.base/callfwmall.exp for platforms without malloc
- To: Keith Seitz <keiths at cygnus dot com>
- Subject: Re: [RFA]: Fix gdb.base/callfwmall.exp for platforms without malloc
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Mon, 21 May 2001 11:10:09 -0700
- CC: Stephane Carrez <Stephane dot Carrez at worldnet dot fr>, gdb-patches at sources dot redhat dot com
- Organization: Red Hat
- References: <Pine.GSO.4.33.0105211053000.16834-100000@ryobi.cygnus.com>
Keith Seitz wrote:
>
> On Mon, 21 May 2001, Michael Snyder wrote:
>
> > No -- but perhaps we could approve a patch that would cause this
> > test to be skipped (or xfailed) for targets in which we know it
> > cannot pass.
>
> Somewhere I am sitting on patches to change the behavior of this to XFAIL
> if malloc does not exist. It does not rely on a particular config
> variable. Instead, it queries gdb if malloc exists in the symbol table.
>
> Would this be better? (Didn't we have this discussion a little while ago?
> Deja vu?)
Yes it did, and no that would not be better. ;-)
The idea of the test is to confirm that GDB can pass the test
even if there is no malloc. I know this is counter-intuitive,
because we are all used to the idea that gdb can NOT pass this
test if there is no malloc -- but apparently there are some
targets (at least one) on which it can.