Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>, shebs@apple.com
Cc: Elena Zannoni <ezannoni@cygnus.com>,
	Kevin Buettner <kevinb@cygnus.com>,
	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:49:00 -0000	[thread overview]
Message-ID: <14987.2963.271054.951247@kwikemart.cygnus.com> (raw)
In-Reply-To: <3A8B07CA.382E04F8@cygnus.com>

Michael Snyder writes:
 > Elena Zannoni wrote:
 > > 
 > > Kevin Buettner writes:
 > >  > 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.)
 > >  >
 > > 
 > > Yes, in callfwmall.c there is this comment:
 > > /* Support program for testing gdb's ability to call functions
 > >    in an inferior which doesn't itself call malloc, pass appropriate
 > >    arguments to those functions, and get the returned result. */
 > > 
 > >  > 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()?
 > > 
 > > HPUX should pass. That's why those tests were added in the first
 > > place, I think.
 > > 
 > >  >
 > >  > If there are some, or if this is a feature that we expect to work (in
 > >  > the fullness of time), then perhaps the FAILing tests ought to be
 > >  > XFAIL'd.  Otherwise, I think Keith's patch is reasonable.
 > >  >
 > > 
 > > Maybe this file should be moved to the gdb.hp directory. But I think
 > > there must have been a reason for which it wasn't put there in the
 > > first place. So I would think it used to pass at some point.
 > > I don't see anything interesting in the ChangeLog.
 > 
 > There was no gdb.hp directory at the time.
 > 

True, but I remember Stan going through and getting files moved around.
Was this file just forgotten?
Stan, do you recall anything about this?


Elena


  reply	other threads:[~2001-02-14 14:49 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 [this message]
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
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=14987.2963.271054.951247@kwikemart.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=fnasser@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@cygnus.com \
    --cc=kevinb@cygnus.com \
    --cc=msnyder@cygnus.com \
    --cc=shebs@apple.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