From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7733 invoked by alias); 5 Apr 2004 20:54:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7317 invoked from network); 5 Apr 2004 20:54:44 -0000 Received: from unknown (HELO otisco.McKusick.COM) (209.31.233.190) by sources.redhat.com with SMTP; 5 Apr 2004 20:54:44 -0000 Received: (from hilfingr@localhost) by otisco.McKusick.COM (8.11.6/8.11.6) id i35KwAU29307; Mon, 5 Apr 2004 13:58:10 -0700 Date: Mon, 05 Apr 2004 20:54:00 -0000 Message-Id: <200404052058.i35KwAU29307@otisco.McKusick.COM> From: "Paul N. Hilfinger" To: Duncan Sands cc: gdb@sources.redhat.com Subject: Re: Building an Ada aware gdb In-Reply-To: Message from Duncan Sands of "Mon, 05 Apr 2004 15:46:29 +0200." <200404051546.29979.baldrick@free.fr> Reply-to: Hilfinger@gnat.com X-SW-Source: 2004-04/txt/msg00032.txt.bz2 > I see that gdb from CVS has some exciting (for me) files > in it: ada-exp.y, ada-lang.h, ada-tasks.c, ada-valprint.c, > ada-lang.c, ada-lex.l, ada-typeprint.c. I would like to build > gdb with Ada support... but how? The only Ada related > configure option seems to be --enable-libada, and that didn't > give me an Ada aware gdb. Does gdb support Ada now? > If so, how to build it... Not yet, but we're finally getting close. At the moment, we are resolving some issues with hooks we'd like to put into non-Ada sources. After that, it's mostly a matter of linking in the Ada modules and testing for regressions on every platform we can get our hands on. A couple of warnings: 1. The current CVS ada-* sources have not been synced with ACT's development versions. This fact has nipped me a couple of times now (including your question), so I should probably update them just so folks can see them. 2. We are turning on Ada support one piece at a time, because there are numerous places where ACT's sources have modifications in non-Ada files that either have to approved for inclusion in public sources or modified to conform to the public sources. These places include full breakpoint support (source file:line will work out of the box) and tasking (where the configuration-management situation will always be at the mercy of threads and their many incarnations). On the other hand, we should have expression evaluation working pretty much. Paul Hilfinger ACT