From: Daniel Jacobowitz <drow@mvista.com>
To: "Daniël Mantione" <daniel@deadlock.et.tudelft.nl>
Cc: Ian Lance Taylor <ian@wasabisystems.com>, gdb@sources.redhat.com
Subject: Re: Stabs: constant string, constant boolean
Date: Tue, 27 Jan 2004 14:14:00 -0000 [thread overview]
Message-ID: <20040127141331.GA22724@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401270931300.14796-100000@deadlock.et.tudelft.nl>
On Tue, Jan 27, 2004 at 09:39:43AM +0100, Daniël Mantione wrote:
>
> On 26 Jan 2004, Ian Lance Taylor wrote:
>
> > Looking at the code, I see that gdb only supports the 'r', 'i', and
> > 'e' types. The 'b', 'c', 's', and 'S' types are documented, but not
> > supported.
> >
> > I note this in the docs:
> >
> > The boolean, character, string, and set constants are not
> > supported by GDB 4.9, but it ignores them.
> >
> > This is not entirely unreasonable, as the 'b', 'c', 's', and 'S' types
> > are short on type information. I think it would normally be better to
> > use 'e' instead of 'b' or 'c'. I suppose that 's' and 'S' aren't seen
> > as an issue since they won't arise in C.
>
> Thanks for the info, even though that is pretty bad news :(
> Constant sets & strings do exist in Pascal, i.e.:
>
> const str1='blablabla';
> set1=['b','l','a'];
>
> I know our former team member Pierre Muller contributed some patches to
> add Pascal support to gdb, but apparently not to support these...
> Alas, Pierre has stopped with Free Pascal development; I'm currently
> trying to give some life-support to the debug-info generation he wrote.
<plug>
If you're working on new code, why not use dwarf2 instead?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-27 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 23:22 Daniël Mantione
2004-01-27 4:20 ` Ian Lance Taylor
2004-01-27 8:39 ` Daniël Mantione
2004-01-27 14:14 ` Daniel Jacobowitz [this message]
2004-01-27 15:27 ` Daniël Mantione
2004-01-27 15:30 ` Daniel Jacobowitz
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=20040127141331.GA22724@nevyn.them.org \
--to=drow@mvista.com \
--cc=daniel@deadlock.et.tudelft.nl \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.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