Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] New command: ``start''
Date: Wed, 19 May 2004 15:36:00 -0000	[thread overview]
Message-ID: <20040519153615.GD10684@gnat.com> (raw)
In-Reply-To: <20040518224131.GA6026@nevyn.them.org>

Hello Daniel,

> > Also, the purpose of this function is slightly different from what
> > I am trying to achieve with the language method: Despite the fact that
> > most users see Ada programs starting at the begining of their main
> > procedure, a closer approximation is that it starts inside procedure
> > main() too. 
> 
> I would say that this was the meaning of main_name, rather than the
> entry point.  Global constructors for C++ traditionally happen before
> the "main program" and don't appear on the backtrace; same seems
> reasonable for Ada.  Without "set backtrace past-main on" you can't see
> the caller of the user's code; that seems reasonable for Ada also.  Do
> you need backtraces to continue to "main"?

Your suggestion makes sense.

> I don't want to proliferate mechanisms.  It would be nice if the debug
> readers could fill this in, and (if necessary, to support existing
> tools) a language specific hook could be called as a fallback.

So let's go for that route. How about:
  1. I add the language-specific hook the way I designed it
     in my last patch.
  2. Use that hook in main_name() when the debug info didn't provide
     the name of the main procedure.
  3. Modify start_command to use main_name() instead of the language
     hook.

Would that work for you?

-- 
Joel


  reply	other threads:[~2004-05-19 15:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18  2:47 Joel Brobecker
2004-05-18  6:32 ` Eli Zaretskii
2004-05-18 17:05   ` Joel Brobecker
2004-05-18 18:42     ` Eli Zaretskii
2004-05-18 19:03       ` Andrew Cagney
2004-05-19  5:39         ` Eli Zaretskii
2004-05-18 19:22       ` Joel Brobecker
2004-05-18 21:47 ` Daniel Jacobowitz
2004-05-18 22:27   ` Joel Brobecker
2004-05-18 22:41     ` Daniel Jacobowitz
2004-05-19 15:36       ` Joel Brobecker [this message]
2004-05-19 15:42         ` Daniel Jacobowitz
2004-05-19 16:10           ` Joel Brobecker
2004-05-20  1:01           ` Joel Brobecker
2004-05-20  5:29             ` Eli Zaretskii
2004-05-20 13:46             ` Daniel Jacobowitz
2004-05-20 16:03               ` Joel Brobecker
2004-05-20 17:14                 ` Daniel Jacobowitz
2004-05-20 20:33                   ` Paul Gilliam
2004-05-20 22:12                   ` Joel Brobecker
2004-05-21  0:26                     ` Daniel Jacobowitz
2004-05-21  1:31                       ` Joel Brobecker
2004-05-24 22:24                         ` Daniel Jacobowitz
2004-05-24 23:57                           ` Joel Brobecker
2004-05-19 14:30 ` Andrew Cagney
2004-05-19 15:39   ` Joel Brobecker
2004-05-19 20:02     ` Eli Zaretskii
2004-05-21 18:57       ` Andrew Cagney
2004-05-18 19:30 Michael Elizabeth Chastain
2004-05-18 19:45 ` Joel Brobecker
2004-05-18 20:21 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=20040519153615.GD10684@gnat.com \
    --to=brobecker@gnat.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