From: Andreas Jaeger <aj@suse.de>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Status of Ada support in GDB?
Date: Mon, 24 Feb 2003 19:24:00 -0000 [thread overview]
Message-ID: <u8y945eb2f.fsf@gromit.moeb> (raw)
In-Reply-To: <20030224175019.GL910@gnat.com> (Joel Brobecker's message of "Mon, 24 Feb 2003 09:50:19 -0800")
Hi Joel,
Joel Brobecker <brobecker@gnat.com> writes:
> Andreas,
>
>> Trying to debug some Ada problems in GCC I noticed that GDB comes with
>> Ada support files but does not link them at all, they just seem to be
>> there for cosmetic :-(
>
> Let me explain a bit the history behind these files, and why they are
> not linked in yet.
Thanks for the background.
> We, at ACT, are the original authors of these files, and have been
> planning on submitting them for inclusion in the FSF tree as soon as
> possible. There is no doubt in our minds that this would be beneficial
> to everybody: the GDB community, the free software community, the Ada
> community, and also ACT itself. So we are trying very hard on our side
> to get this done. Unfortunately, due to commercial pressure and lack of
> resources, we haven't be able to get this done yet.
>
> So maybe a year ago, ACT made a "code dropping": our sources-du-jour
> were made available for download on the sources.redhat.com ftp site.
> The hope was that some people might find it useful, while we keep making
> progress on cleaning up our code to get it to a state where it would be
> acceptable for inclusion.
>
> Somebody outside of ACT actually volunteered to merge these changes into
> the FSF tree for us. He started by first sending a new patch that was
> this time against the current sources (instead of current against an old
> 5.1 snapshot). He then checked in the ada-* files, and started cleaning
> them up. The plan was for him to (more or less): cleanup these files,
> add the bits in the makefiles to compile them in, and then activate
> slowly all the ada functionality. Unfortunately, as it often happens,
> this volunteer found a day job, and found that he could not spend time
> on this task anymore.
>
> So ACT is picking up the task again. We are getting much closer to
> having something we can submit, one of our part-time consultant is
> working full-time (if I may say so) on it. In the meantime, could you
I'm glad to hear about this commitment!
> try using the 5.1.1-based sources that we made available through
> sources.redhat.com?
I need a gdb to debug problems on x86-64 - and that architecture is
only supported since gdb 5.2, so your 5.1.1 changes will not help me
directly,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2003-02-24 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 8:40 Andreas Jaeger
2003-02-24 17:50 ` Joel Brobecker
2003-02-24 19:24 ` Andreas Jaeger [this message]
2003-02-25 21:31 ` Joel Brobecker
2003-02-25 21:39 ` Andrew Cagney
2003-02-24 22:46 ` Stephane Carrez
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=u8y945eb2f.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=brobecker@gnat.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