From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: FPC Core Developer List <core@freepascal.org>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>,
<gdb-patches@sourceware.org>,
gpc@gnu.de
Subject: Re: [Core] [RFA/DWARF2] Handle nested subprograms in CU pc bound calculation
Date: Wed, 01 Oct 2008 08:33:00 -0000 [thread overview]
Message-ID: <BA00E108-B2B3-4CA4-8EAB-99D0B4200964@elis.ugent.be> (raw)
In-Reply-To: <003201c92399$3207f300$9617d900$@u-strasbg.fr>
On 01 Oct 2008, at 09:42, Pierre Muller wrote:
> De : Joel Brobecker [mailto:brobecker@adacore.com]
>
>> This is only just for comments, as there is still one question open:
>> For Ada, we store the symbols for nested subprograms in the global
>> context. This allows us to break on these functions even when these
>> functions are not defined in the current context. Do we want to do
>> the
>> same with Pascal?
>
> I believe that, at least with the Free Pascal compiler and
> stabs debugging format (which is the format I worked on), all
> nested subprograms where also in the global context and thus
> I would not mind to do the same for pascal language.
>
> I must confess that I stopped working for the Free Pascal compiler
> more or less when the dwarf debugging format was added, and I almost
> don't
> know
> anything about that format...
> The only thing that I can tell, is that last time I checked
> Free Pascal (version 2.2.0 windows 32bit target) with -gw (dwarf
> debugging
> format)
> I still got lots of errors while trying to load the compiler inside
> gdb :(
At least under Mac OS X, FPC with dwarf works fairly well. I believe
it works ok under Linux too. I don't know about win32.
> I must confess that I don't even know if the full specification
> would work for pascal in case the same name is used globally and as
> a nested procedure (I do know that you are allowed
> to reuse a name defined globally as a local procedure, function or
> variable
> inside a function, but I don't know if the
> (gdb) break GlobalFuntion.LocalFunction
> would work)
It doesn't work with FPC and stabs under 6.6-45.fc8rh at least
(neither when using only upper case nor when using the casing as it
appears in the source code). Was support for this only added in a
later gdb version?
Jonas
next prev parent reply other threads:[~2008-10-01 8:33 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 ` Jonas Maebe [this message]
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
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=BA00E108-B2B3-4CA4-8EAB-99D0B4200964@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=brobecker@adacore.com \
--cc=core@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