From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Andrzej Borucki <borucki.andrzej@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Pascal property
Date: Mon, 15 Apr 2013 14:48:00 -0000 [thread overview]
Message-ID: <09D287BA-1A15-4893-BA30-D66472B6169F@elis.ugent.be> (raw)
In-Reply-To: <CAE2KeAJd_rtN64CCk2EONAH2uuK2TUoBZacHa292K0q=6eAd-A@mail.gmail.com>
On 13 Apr 2013, at 09:19, Andrzej Borucki wrote:
> It possible to handle Pascal property in Lazarus with GDB? I must call
> function with object parameter. Sometimes function can return string
> or dynamic array.
Afaik, the DWARF debug info format does not support "properties" (for
non-Delphi-style-Pascalites: properties in this language are
identifiers with which you can associate a getter and/or setter that
can both be arbitrarily named). Additionally, Free Pascal/Delphi-style
ansistring and dynamic arrays would require (FPC-specific) support to
be added to GDB to handle the reference counting for these types. I'm
not aware of anyone working on support for this.
Jonas
prev parent reply other threads:[~2013-04-15 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 7:19 Andrzej Borucki
2013-04-15 14:48 ` Jonas Maebe [this message]
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=09D287BA-1A15-4893-BA30-D66472B6169F@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=borucki.andrzej@gmail.com \
--cc=gdb@sourceware.org \
/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