From: Joel Brobecker <brobecker@adacore.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Improve "start" command for Ada
Date: Tue, 08 Mar 2005 04:40:00 -0000 [thread overview]
Message-ID: <20050308044006.GC1750@adacore.com> (raw)
In-Reply-To: <16940.49472.585572.202096@localhost.redhat.com>
Just to confirm that I just checked in the following patch:
2005-03-07 Joel Brobecker <brobecker@adacore.com>
* doc/observer.texi (executable_changed): New observer.
* symtab.c: Include "observer.h".
(find_main_name): New function.
(main_name): If name_of_main is unset, then compute it
using find_main_name.
(symtab_observer_executable_changed): New function.
(_initialize_symtab): Attach executable_changed observer.
* exec.c: Include "observer.h".
(exec_file_attach): Emit executable_changed notification.
* symfile.c: Include "observer.h".
(reread_symbols): Send an executable_changed if appropriate.
* Makefile.in (exec.o): Add dependency on observer.h.
(symfile.o): Likewise.
(symtab.o): Likewise.
This fixes the following 2 FAILs:
FAIL: gdb.ada/null_record.exp: start (PRMS ada/1892)
FAIL: gdb.ada/start.exp: start (PRMS ada/1892)
Here is the comment that I added:
/* FIXME: brobecker/2005-03-07: Another way of doing this would
be to add a new method in the language vector, and call this
method for each language until one of them returns a non-empty
name. This would allow us to remove this hard-coded call to
an Ada function. It is not clear that this is a better approach
at this point, because all methods need to be written in a way
such that false positives never be returned. For instance, it is
important that a method does not return a wrong name for the main
procedure if the main procedure is actually written in a different
language. It is easy to guaranty this with Ada, since we use a
special symbol generated only when the main in Ada to find the name
of the main procedure. It is difficult however to see how this can
be guarantied for languages such as C, for instance. This suggests
that order of call for these methods becomes important, which means
a more complicated approach. */
--
Joel
next prev parent reply other threads:[~2005-03-08 4:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 3:48 Joel Brobecker
2004-10-21 5:31 ` Eli Zaretskii
2004-10-21 21:09 ` Joel Brobecker
2004-10-23 10:05 ` Eli Zaretskii
2004-11-01 19:47 ` Joel Brobecker
2004-11-29 2:12 ` Elena Zannoni
2004-12-01 3:03 ` Joel Brobecker
2005-02-09 18:22 ` Joel Brobecker
2005-03-07 19:30 ` Joel Brobecker
2005-03-07 20:59 ` Elena Zannoni
2005-03-07 21:12 ` Joel Brobecker
2005-03-08 4:40 ` Joel Brobecker [this message]
2004-11-22 19:10 ` 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=20050308044006.GC1750@adacore.com \
--to=brobecker@adacore.com \
--cc=ezannoni@redhat.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