From: Michael Snyder <msnyder@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Fernando Nasser <fnasser@cygnus.com>,
Keith Seitz <keiths@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Assuming malloc exists in callfwmall.exp
Date: Wed, 14 Feb 2001 14:34:00 -0000 [thread overview]
Message-ID: <3A8B07DC.B6BE7482@cygnus.com> (raw)
In-Reply-To: <1010214211043.ZM6538@ocotillo.lan>
Kevin Buettner wrote:
>
> On Feb 14, 12:51pm, Michael Snyder wrote:
>
> > Fernando Nasser wrote:
> > >
> > > Sounds reasonable. Check it in (assuming you have already added yourself to the write after approval list).
> >
> > Hold on -- aren't you defeating the purpose of this test?
> > The test was added by HP precisely because these calls
> > fail when malloc isn't included in the target program.
> > The test is a duplicate of callfuncs.exp, except that it
> > doesn't link malloc.
>
> I sort of agree with Michael. (I almost posted a similar remark.)
>
> OTOH, given that GDB's mechanism for performing these tests is to
> use malloc(), I'm not sure how these are supposed to succeed. (As
> someone else pointed out, they do succeed on some platforms because
> malloc() sneaks into the picture through the dynamic loader.)
>
> Does anyone know of any host/target combinations which manage to pass
> these tests without using malloc()?
I would assume that the tests pass on HPUX, else HP would not
have added them. But I don't know if they bothered to ascertain
whether the tests could be made to pass on any other platform.
next prev parent reply other threads:[~2001-02-14 14:34 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.3.91.1010214082014.13194C-100000@ryobi.cygnus.com>
2001-02-14 9:02 ` Fernando Nasser
2001-02-14 12:52 ` Michael Snyder
2001-02-14 13:10 ` Kevin Buettner
2001-02-14 13:28 ` Elena Zannoni
2001-02-14 13:41 ` Kevin Buettner
2001-02-14 14:00 ` Elena Zannoni
2001-02-14 20:13 ` Andrew Cagney
2001-02-15 1:14 ` Fernando Nasser
2001-02-15 10:34 ` Andrew Cagney
2001-02-14 14:33 ` Michael Snyder
2001-02-14 14:49 ` Elena Zannoni
2001-02-14 14:34 ` Michael Snyder [this message]
2001-02-14 13:12 ` Keith Seitz
2001-02-14 13:20 ` Fernando Nasser
2001-02-14 13:37 ` Stan Shebs
2001-02-14 13:46 ` Fernando Nasser
2001-02-14 14:35 ` Michael Snyder
2001-02-14 9:06 Michael Elizabeth Chastain
2001-02-14 9:07 ` Keith Seitz
2001-02-14 9:11 ` Fernando Nasser
2001-02-14 13:41 Michael Elizabeth Chastain
2001-02-14 14:17 Michael Elizabeth Chastain
2001-02-14 14:37 ` Kevin Buettner
2001-02-14 15:12 Michael Elizabeth Chastain
2001-02-14 16:29 Michael Elizabeth Chastain
2001-02-14 18:17 ` Andrew Cagney
2001-02-14 18:35 Michael Elizabeth Chastain
2001-02-14 19:27 Michael Elizabeth Chastain
2001-02-15 1:06 ` Fernando Nasser
2001-02-15 1:22 ` Fernando Nasser
2001-02-15 6:54 ` Kevin Buettner
2001-02-15 7:06 Michael Elizabeth Chastain
2001-02-15 7:32 ` Fernando Nasser
2001-02-15 7:09 Michael Elizabeth Chastain
2001-02-15 7:54 Michael Elizabeth Chastain
2001-02-15 8:09 ` Fernando Nasser
2001-02-15 8:30 Michael Elizabeth Chastain
2001-02-15 8:45 ` Fernando Nasser
2001-02-15 9:00 Michael Elizabeth Chastain
2001-02-15 11:53 ` Fernando Nasser
2001-02-15 11:56 ` Jim Blandy
2001-02-15 12:08 Michael Elizabeth Chastain
2001-02-15 12:41 ` Fernando Nasser
2001-02-15 12:16 Michael Elizabeth Chastain
2001-02-15 23:36 ` Eli Zaretskii
2001-02-15 12:30 Michael Elizabeth Chastain
2001-02-15 12:48 ` Fernando Nasser
2001-02-15 12:56 Michael Elizabeth Chastain
2001-02-16 8:51 ` Jim Blandy
2001-02-15 12:58 Michael Elizabeth Chastain
2001-02-15 19:05 Michael Elizabeth Chastain
2001-02-16 8:36 ` Jim Blandy
2001-02-16 8:41 Michael Elizabeth Chastain
2001-02-16 8:55 Michael Elizabeth Chastain
2001-02-16 9:48 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A8B07DC.B6BE7482@cygnus.com \
--to=msnyder@cygnus.com \
--cc=fnasser@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@cygnus.com \
--cc=kevinb@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox