public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gulsenenginar at aol dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26901] Array subscript fails with flexible array member without size
Date: Sat, 09 Oct 2021 11:00:39 +0000	[thread overview]
Message-ID: <bug-26901-4717-68wh63Qe13@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26901-4717@http.sourceware.org/bugzilla/>

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

Gulsen Engin <gulsenenginar at aol dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gulsenenginar at aol dot com

--- Comment #12 from Gulsen Engin <gulsenenginar at aol dot com> ---
gdb: fix value_subscript when array upper bound is not known
http://www-look-4.com/category/health/

    Since commit 7c6f27129631 ("gdb: make get_discrete_bounds check for
https://komiya-dental.com/category/crypto/ 
    non-constant range bounds"), subscripting  flexible array member fails:
    http://www.iu-bloomington.com/category/health/
        struct no_size
        { https://waytowhatsnext.com/category/health/
          int n;
          int items[];
        };
     http://www.wearelondonmade.com/category/health/
        (gdb) p *ns
        $1 = {n = 3, items = 0x5555555592a4}
        (gdb) p ns->items[0] http://www.jopspeech.com/category/health/
        Cannot access memory at address 0xfffe555b733a0164
        (gdb) p *((int *) 0x5555555592a4)
        $2 = 101  <--- we would expect that http://joerg.li/category/health/
        (gdb) p &ns->items[0]
        $3 = (int *) 0xfffe5559ee829a24  <--- wrong address
http://connstr.net/category/health/

    Since the flexible array member (items) has an unspecified size, the array
type
    created for it in the DWARF doesn't have dimensions (this is with gcc
9.3.0, http://embermanchester.uk/category/health/
    Ubuntu 20.04):
    http://www.slipstone.co.uk/category/health/
        0x000000a4:   DW_TAG_array_type
                        DW_AT_type [DW_FORM_ref4]       (0x00000038 "int")
                        DW_AT_sibling [DW_FORM_ref4]    (0x000000b3)
http://www.logoarts.co.uk/category/health/

        0x000000ad:     DW_TAG_subrange_type
                          DW_AT_type [DW_FORM_ref4]     (0x00000031 "long
unsigned int")
    http://www.acpirateradio.co.uk/category/health/
    This causes GDB to create a range type (TYPE_CODE_RANGE) with a defined
    constant low bound (dynamic _prop with kind PROP_CONST) and an undefined
    high bound (dynamic_prop with kind PROP_UNDEFINED).
http://www.compilatori.com/category/health/

    value_subscript gets both bounds of that range using
    get_discrete_bounds.  Before commit 7c6f27129631, get_discrete_bounds
    didn't check the kind of the dynamic_props and would just blindly read
    them as if they were PROP_CONST.
https://www.webb-dev.co.uk/category/health/  It would return 0 for the high
bound,
    because we zero-initialize the range_bounds structure.  And it didn't
    really matter in this case, because the returned high bound wasn't used
    in the end.


https://pro-sangyoui.com/
https://fintechzoom.com/reviews/15-best-water-bottles-of-2021/
https://fintechzoom.com/reviews/10-best-yoga-mats-of-2021/
https://wikifinancepedia.com/
https://financeplusinsurance.com/
https://financeinsuranceblog.com/
https://fintechzoom.com/reviews/the-greatest-robot-vacuums-for-assure-cleaner-floors/
https://fintechzoom.com/reviews/the-11-best-air-purifiers-in-2021/
https://fintechzoom.com/reviews/the-6-best-cordless-stick-vacuum-in-2021/
https://amazon.com/Christopher-Horne/e/B08D6C1D2P%3Fref=dbs_a_mng_rwt_scns_share
https://nhacai888b.com/
https://www.soicau888.net/
https://kaiyokukan.vn/
http://twin688.net/
https://typhu88.me/
https://fitveform.com/
https://www.thegamblinggurus.com/
https://nodepositpokeronline.com/
https://onlinecasinoku.com/
https://slickcashloanca.blogspot.com/
https://www.aaz-credit-immobilier.com/
https://www.sport-trader.com/
https://www.lespersiennes.com/
https://www.espresso-international.it/
https://www.espresso-international.fi/
https://footballexpress.in/category/indian-football/
https://sixsports.in/category/cricket/
https://true-tech.net/
https://www.alivechristians.com/bible-verses-about-healing-sickness/
https://photoslate.co/
https://trellising-net.com/
https://www.seminariostop.com/seminarios-y-talleres/como-importar-de-china-alibaba-aliexpress-dropshipping-peru/
https://bestonlinegambler.com/
https://vipcasinotips.com/
https://casinogamblingideas.com/
https://realmoneycasinoguides.com/
https://casinoexpertadvice.com/
https://komopoker5.com/
https://zehabesha.com/

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

  parent reply	other threads:[~2021-10-09 11:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15  2:47 [Bug gdb/26901] New: Python array " simark at simark dot ca
2020-11-15  2:50 ` [Bug gdb/26901] Array " simark at simark dot ca
2020-11-15  2:50 ` simark at simark dot ca
2020-11-16 18:21 ` simark at simark dot ca
2020-12-03 19:01 ` simark at simark dot ca
2020-12-09 18:53 ` cvs-commit at gcc dot gnu.org
2020-12-09 21:34 ` cvs-commit at gcc dot gnu.org
2020-12-09 22:11 ` simark at simark dot ca
2021-06-27 18:00 ` ahmedsayeed1982 at yahoo dot com
2021-08-10 12:45 ` ucelsanicin at yahoo dot com
2021-09-02 11:06 ` donipah907 at mtlcz dot com
2021-09-02 11:16 ` mark at klomp dot org
2021-09-06  9:09 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:39 ` mehmetgelisin at aol dot com
2021-09-22 10:19 ` diheto5497 at secbuf dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com [this message]
2021-10-17 19:49 ` vmireskazki at gmail dot com
2021-10-19  7:15 ` progonsaytu at gmail dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-11-25 13:58 ` mdxconcepts0008 at gmail dot com

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-26901-4717-68wh63Qe13@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).