This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] Assuming malloc exists in callfwmall.exp
- To: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Subject: Re: [RFA] Assuming malloc exists in callfwmall.exp
- From: Fernando Nasser <fnasser at redhat dot com>
- Date: Thu, 15 Feb 2001 11:42:35 -0500
- CC: ac131313 at cygnus dot com, gdb-patches at sources dot redhat dot com, keiths at cygnus dot com
- Organization: Red Hat Canada
- References: <200102151630.IAA22826@bosch.cygnus.com>
Michael Elizabeth Chastain wrote:
>
> > (#3 does not depend on malloc() so it is already tested in callfuncs).
>
> No. Look at use case #3:
>
> Use case #3:
>
> . malloc is not available
> . the user types: call abs(-10)
> . gdb expected response: "$1 = 10"
>
> callfuncs.c contains an explicit call to malloc. Therefore, callfuncs.exp
> does not check use case #3. It checks use case #1.
I don't get it. malloc is not used at all when the argument is not a
string. So, what malloc() being available or not has to do with this
situation?
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9