From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 48B94385773C; Mon, 21 Aug 2023 10:18:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 48B94385773C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1692613124; bh=uR1+YGbcao/LSV5Ru2Wrfzh/+SBKAZ5HbNC5KL1kznY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AeN5KCY4H2NFfy97iNRksbpHLUTX82mTRrlD2OoZQdM8np962rhLYYHvSbs+oE0yr yxlbKxNCMYJZat1EwSyr6uHs7TRT7ls1YBG1G7YHtFKCGzYdgfHyQ6VYXnEXUtyZUP 785poucLBlGz96e2ao0kjnkzUR8XSTJLS5zT2A2s= From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30775 --- Comment #1 from Tom de Vries --- 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 =3D false" setup. ] This requires us to explicitly mark nullptr parent, which turns out to be n= ot 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) =3D=3D nullptr &&=20 (outside_valid_range (offset) || (inside_valid_range (offset) and m_deferred_entries.find (offset)) ... --=20 You are receiving this mail because: You are on the CC list for the bug.=