public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30775] [gdb/symtab] Cannot distinguish between nullptr and dont-know in m_die_range_map
Date: Mon, 21 Aug 2023 10:18:43 +0000	[thread overview]
Message-ID: <bug-30775-4717-Hend285jhZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30775-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
My first attempt at this was to encode nullptr parent as (void *)-1.  [ That
would have made m_die_range_map much bigger, so I started out with a "const
bool m_die_range_map_verify = false" setup. ]

This requires us to explicitly mark nullptr parent, which turns out to be not
nicely isolated in a few spots.

So my current thinking is to maintain a valid_range object alongside
m_die_range_map, and represent the "don't know the parent" case by:
...
(m_die_range_map.find (offset) == nullptr && 
  (outside_valid_range (offset)
   || (inside_valid_range (offset) and m_deferred_entries.find (offset))
...

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

      reply	other threads:[~2023-08-21 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 11:21 [Bug symtab/30775] New: " vries at gcc dot gnu.org
2023-08-21 10:18 ` vries at gcc dot gnu.org [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=bug-30775-4717-Hend285jhZ@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).