From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: FPC Core Developer List <core@freepascal.org>
Cc: Pierre Muller <muller@ics.u-strasbg.fr>,
gpc@gnu.de, gdb-patches@sourceware.org
Subject: Re: [Core] [RFA/DWARF2] Handle nested subprograms in CU pc bound calculation
Date: Wed, 01 Oct 2008 21:56:00 -0000 [thread overview]
Message-ID: <93E24692-A1FE-4078-A76F-92AAF92AB4ED@elis.ugent.be> (raw)
In-Reply-To: <20081001163945.GI3665@adacore.com>
On 01 Oct 2008, at 18:39, Joel Brobecker wrote:
> The answer to the question above lies in the Pascal parser. But when
> there are homonyms, how do you specify in your program exactly which
> one you mean?
unitname.functionname
> And does GDB provide the same method for distinguishing
> these homonyms?
I don't think so. The main problem is that there is no common way of
mangling procedure/function names in Pascal. FPC and GPC mangle them
in different ways, and as far as I know gdb has no support to demangle
either (it definitely does not support demangling FPC names).
For this reason, I always use either symbol names or sourcefile:linenr
to place breakpoints.
Jonas
next prev parent reply other threads:[~2008-10-01 21:56 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 ` Daniel Jacobowitz
2008-09-30 16:56 ` Joel Brobecker
2008-09-30 17:05 ` Daniel Jacobowitz
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 ` Jonas Maebe [this message]
2008-10-02 6:45 ` [Core] " 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 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=93E24692-A1FE-4078-A76F-92AAF92AB4ED@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=core@freepascal.org \
--cc=gdb-patches@sourceware.org \
--cc=gpc@gnu.de \
--cc=muller@ics.u-strasbg.fr \
/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