From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sources.redhat.com
Subject: Re: Ada and the "start" command
Date: Sun, 06 Mar 2005 21:44:00 -0000 [thread overview]
Message-ID: <20050306214421.GL1750@adacore.com> (raw)
In-Reply-To: <20050306213511.GA13223@nevyn.them.org>
> > Do any of the gdb.ada tests pass for you, using a clean GDB tree? My
> > impression is that the "start" command, upon which they all rely, can
> > not possibly work in FSF GDB. There's ada_main_name, which correctly
> > digs the name out of the executable, but it isn't hooked up to
> > anything. So "start" always goes to "main".
> >
> > If the tests can't work in this tree, they should be disabled. I'm not
> > sure what the plan for ada_main_name is.
>
> Scratch the last sentence; I found the pending patch on gdb-patches. I
> still do not like tests which will not yet pass being added to the
> source tree.
I know what you mean.
At the time the test was added, the test was supposed to be failing for
a short period of time, because it was felt that the problem be fixed
quickly (we had discussed on how we were going to hook that up and
agreed on a plan). Since then, Elena jumped in, approved almost
everything, except one bit. I answered her message, but never received
any response, even after a couple of pings.
We can do two things: Either have somebody else than Elena approve
(or comment) on the patch, or KFAIL the tests. Do you think you can
approve the rest of the patch?
--
Joel
next prev parent reply other threads:[~2005-03-06 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 21:34 Daniel Jacobowitz
2005-03-06 21:35 ` Daniel Jacobowitz
2005-03-06 21:44 ` Joel Brobecker [this message]
2005-03-06 22:07 ` Daniel Jacobowitz
2005-03-07 3:16 ` Joel Brobecker
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=20050306214421.GL1750@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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