Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Daniël Mantione" <daniel.mantione@freepascal.org>
Cc: FPC Core Developer List <core@freepascal.org>,
	gpc@gnu.de, 	gdb-patches@sourceware.org
Subject: Re: [Core] [RFA/DWARF2] Handle nested subprograms in CU pc bound  calculation
Date: Fri, 03 Oct 2008 00:31:00 -0000	[thread overview]
Message-ID: <20081003003018.GP3665@adacore.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0810021109140.13206@idefix.wisa.be>

> All information the compiler has available is inside the ppu and the debug 
> information is generated from it. We should simply place anything GDB 
> needs into the debug information.

OK.  Thanks to everyone who participated in the discussion. I pretty
much agree with the above.

Until then, I would suggest that we do not put the nested subprograms
in the global scope, as nested subprogram names might collide with
global functions that have the same name.  But if the Pascal users
feel differently, then it's easy to fix.

-- 
Joel


  reply	other threads:[~2008-10-03  0:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 15:28 Joel Brobecker
2008-09-30 15:43 ` Pierre Muller
2008-09-30 17:07   ` Joel Brobecker
2008-09-30 17:39     ` Daniel Jacobowitz
2008-10-01  1:16       ` Joel Brobecker
2008-10-01  7:43         ` Pierre Muller
2008-10-01  8:33           ` [Core] " Jonas Maebe
2008-10-01 16:40           ` Joel Brobecker
2008-10-01 21:56             ` [Core] " Jonas Maebe
2008-10-02  6:45             ` Daniël Mantione
2008-10-02  9:07               ` Pierre Muller
2008-10-02 10:36                 ` Daniël Mantione
2008-10-03  0:31                   ` Joel Brobecker [this message]
2008-09-30 15:43 ` Daniel Jacobowitz
2008-09-30 16:56   ` Joel Brobecker
2008-09-30 17:05     ` Daniel Jacobowitz
2008-09-30 16:58 ` 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=20081003003018.GP3665@adacore.com \
    --to=brobecker@adacore.com \
    --cc=core@freepascal.org \
    --cc=daniel.mantione@freepascal.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gpc@gnu.de \
    /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