From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Subject: Re: [RFA] Fix display of array of unspecified length inside structures
Date: Fri, 18 Feb 2011 11:59:00 -0000 [thread overview]
Message-ID: <201102181147.52337.pedro@codesourcery.com> (raw)
In-Reply-To: <00ac01cbcf5c$31f5bc00$95e13400$@muller@ics-cnrs.unistra.fr>
On Friday 18 February 2011 11:08:38, Pierre Muller wrote:
> PS: It could be wise to add some test in the testsuite for
> this, but I have no idea where I could insert this kind of test,
> any ideas?
Yes, please. We have surprisingly few tests for this sort of
thing, AFAICS. I'm not even sure this is a regression from
my recent changes, I think it may well not be.
Zero-length arrays (as poor man's flexible arrays) are supported
in GNU C as an extension. To be portable, you'd
need to use an array of length 1 (or c99's real flexible arrays),
but that won't trigger the bug.
I'd point at printcmds.exp, but I'm not sure if there are compilers
out there that choke on the construct... There's always a
new test file option...
> PS2: It is probably impossible to make such a test without
> alloca or some other memory allocation function, no?
> Are there any system restriction for this?
Should be fine.
> 2011-02-18 Pierre Muller <muller@ics.u-strasbg.fr>
>
> * c-valprint.c (c_val_print): Add embedded_offset to address
> for arrays of unspecified length.
> * p-valprint.c (pascal_val_print): Likewise.
Okay, thanks.
--
Pedro Alves
next prev parent reply other threads:[~2011-02-18 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 11:34 Pierre Muller
2011-02-18 11:59 ` Pedro Alves [this message]
2011-02-18 15:01 ` Pierre Muller
2011-02-18 15:38 ` Pedro Alves
2011-02-18 17:39 ` Pierre Muller
2011-02-18 17:41 ` Pedro Alves
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=201102181147.52337.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.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