From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: ac131313@cygnus.com, chastain@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Assuming malloc exists in callfwmall.exp
Date: Wed, 14 Feb 2001 18:35:00 -0000 [thread overview]
Message-ID: <200102150235.SAA07020@bosch.cygnus.com> (raw)
Argh. Let me say that again:
chastain> (1) Test for the presence of malloc the way Keith Seitz is doing
chastain> (but put the test after runto_main).
cagney> it is testing exactly what it should be testing but the above would
cagney> disable malloc for this target.
I'm proposing that Keith move the "p malloc" line *after* the call
to "runto_main". That would detect that malloc was available in the
inferior.
If malloc is available in the inferior, then callfwmall.exp should
stop execution. If malloc is not available, then callfwmall.exp can
continue testing that gdb can make inferior calls in a target program
that does not have malloc.
Michael
next reply other threads:[~2001-02-14 18:35 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 18:35 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 9:48 Michael Elizabeth Chastain
2001-02-16 8:55 Michael Elizabeth Chastain
2001-02-16 8:41 Michael Elizabeth Chastain
2001-02-15 19:05 Michael Elizabeth Chastain
2001-02-16 8:36 ` Jim Blandy
2001-02-15 12:58 Michael Elizabeth Chastain
2001-02-15 12:56 Michael Elizabeth Chastain
2001-02-16 8:51 ` Jim Blandy
2001-02-15 12:30 Michael Elizabeth Chastain
2001-02-15 12:48 ` Fernando Nasser
2001-02-15 12:16 Michael Elizabeth Chastain
2001-02-15 23:36 ` Eli Zaretskii
2001-02-15 12:08 Michael Elizabeth Chastain
2001-02-15 12:41 ` 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 8:30 Michael Elizabeth Chastain
2001-02-15 8:45 ` Fernando Nasser
2001-02-15 7:54 Michael Elizabeth Chastain
2001-02-15 8:09 ` Fernando Nasser
2001-02-15 7:09 Michael Elizabeth Chastain
2001-02-15 7:06 Michael Elizabeth Chastain
2001-02-15 7:32 ` Fernando Nasser
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-14 16:29 Michael Elizabeth Chastain
2001-02-14 18:17 ` Andrew Cagney
2001-02-14 15:12 Michael Elizabeth Chastain
2001-02-14 14:17 Michael Elizabeth Chastain
2001-02-14 14:37 ` Kevin Buettner
2001-02-14 13:41 Michael Elizabeth Chastain
2001-02-14 9:06 Michael Elizabeth Chastain
2001-02-14 9:07 ` Keith Seitz
2001-02-14 9:11 ` Fernando Nasser
[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
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
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=200102150235.SAA07020@bosch.cygnus.com \
--to=chastain@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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