public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mockbutler at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/30404] New: Incorrect evaluation of sizeof(*pointer) for structure with zero length array
Date: Sat, 29 Apr 2023 11:19:54 +0000	[thread overview]
Message-ID: <bug-30404-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30404

            Bug ID: 30404
           Summary: Incorrect evaluation of sizeof(*pointer) for structure
                    with zero length array
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: exp
          Assignee: unassigned at sourceware dot org
          Reporter: mockbutler at gmail dot com
  Target Milestone: ---

Created attachment 14856
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14856&action=edit
Use with gdb to demonstrate bug.

When the last element of a C language struct is a zero length array, the
evaluation of sizeof(*(struct S*)pointer) does not match sizeof(struct S).

> Breakpoint 1, fn (ps=0x7fffffffe250) at demo-sizeof-bug.c:15
> 15              printf("ps = %p\n", ps);
> (gdb) p sizeof(*ps)
> $1 = 7
> (gdb) p sizeof(struct S)
> $2 = 8
> (gdb) ptype/o *ps
> /* offset      |    size */  type = struct S {
> /*      0      |       4 */    int32_t f1;
> /*      4      |       2 */    int16_t f2;
> /*      6      |       1 */    int8_t f3;
> /*      7      |       0 */    int8_t f4[];
>                              /* total size (bytes):    7 */

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2023-04-29 11:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-30404-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).