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 gdb/31237] [gdb, clang] FAIL: gdb.gdb/index-file.exp: gdb-index files are identical
Date: Sat, 13 Jan 2024 14:54:54 +0000	[thread overview]
Message-ID: <bug-31237-4717-XYlxJHBLy2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31237-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, there's an actual difference in the address table:
...
$ grep " 122$" 1 | sort -d
000000000043ac80 000000000043ad48 122
00000000006bbeb0 00000000006bd024 122
00000000028d4aa8 00000000028d4aa9 122
00000000028d4b50 00000000028d4b51 122
0000000002b74880 0000000002b74881 122
0000000002b74888 0000000002b74889 122
$ grep " 122$" 2 | sort -d
00000000006bbeb0 00000000006bd024 122
00000000028d4aa8 00000000028d4aa9 122
00000000028d4b50 00000000028d4b51 122
0000000002b74880 0000000002b74881 122
0000000002b74888 0000000002b74889 122
...
The first element of 1 is extra, the rest of the entries is equal.

Let's grep for the starting address of the extra element: 
...
$ grep 43ac80 1
000000000043ac80 000000000043ad48 122
000000000043ac80 000000000043ace8 244
000000000043ac80 000000000043b1c4 490
000000000043ac80 000000000043ad48 600
$ grep 43ac80 2
000000000043ac80 000000000043ace8 244
000000000043ac80 000000000043b1c4 490
...

So, for a given address 0x43ac80 there is a number of CUs that match, and the
number is different between the two address tables.

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

  parent reply	other threads:[~2024-01-13 14:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12  8:13 [Bug gdb/31237] New: " vries at gcc dot gnu.org
2024-01-12 10:18 ` [Bug gdb/31237] " vries at gcc dot gnu.org
2024-01-12 10:19 ` vries at gcc dot gnu.org
2024-01-12 16:03 ` tromey at sourceware dot org
2024-01-13  1:56 ` tromey at sourceware dot org
2024-01-13 14:25 ` vries at gcc dot gnu.org
2024-01-13 14:54 ` vries at gcc dot gnu.org [this message]
2024-01-16  7:42 ` vries at gcc dot gnu.org
2024-01-16 10:55 ` vries at gcc dot gnu.org
2024-01-16 12:36 ` vries at gcc dot gnu.org

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-31237-4717-XYlxJHBLy2@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).