From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>
Cc: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 0/2] Write DWARF index cache files in background
Date: Fri, 3 Mar 2023 12:52:08 -0500 [thread overview]
Message-ID: <ca45fa11-17c2-a95f-3d46-b754ce35d561@simark.ca> (raw)
In-Reply-To: <87cz5pagkr.fsf@tromey.com>
On 3/3/23 12:29, Tom Tromey via Gdb-patches wrote:
> Simon> I don't understand this.
>
> Yeah, sorry, I didn't properly understand the test.
>
> Simon> I think this could be solved with a maintenance command to explicitly
> Simon> wait for index cache creation (calls wait_for_index_cache). I don't see
> Simon> another reliable way. What do you think? I can implement it if you
> Simon> think it would work.
>
> I think you're right. I can handle it.
I spotted another failure, when running with native-extended-gdbserver:
254 (gdb) file /home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/index-cache/index-cache^M
255 Reading symbols from /home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/index-cache/index-cache...^M
256 /home/smarchi/src/binutils-gdb/gdb/gdbtypes.h:967: internal-error: field: Assertion `idx >= 0 && idx < num_fields ()' failed.^M
257 A problem internal to GDB has been detected,^M
258 further debugging may prove unreliable.^M
259 ERROR: Couldn't load index-cache into GDB (GDB internal error).
I don't know why it would be specific to native-extended-gdbserver,
maybe it changes the timing in just the right (wrong) way. I haven't
dug into it yet.
Simon
prev parent reply other threads:[~2023-03-03 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 16:45 Tom Tromey
2022-12-19 16:45 ` [PATCH v3 1/2] Only use the per-BFD object to write a DWARF index Tom Tromey
2022-12-19 16:45 ` [PATCH v3 2/2] Write the DWARF index in the background Tom Tromey
2023-02-24 18:46 ` [PATCH v3 0/2] Write DWARF index cache files in background Tom Tromey
2023-02-24 21:44 ` Simon Marchi
2023-03-02 15:51 ` Tom Tromey
2023-03-03 16:41 ` Tom Tromey
2023-03-03 17:22 ` Simon Marchi
2023-03-03 17:29 ` Tom Tromey
2023-03-03 17:52 ` Simon Marchi [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=ca45fa11-17c2-a95f-3d46-b754ce35d561@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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).