From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Alexandra Petlanova Hajkova <ahajkova@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Handle DWARF 5 separate debug sections
Date: Tue, 22 Apr 2025 08:55:27 -0600 [thread overview]
Message-ID: <871ptk8cv4.fsf@tromey.com> (raw)
In-Reply-To: <874iz548dq.fsf@tromey.com> (Tom Tromey's message of "Thu, 03 Apr 2025 08:39:13 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>>>>> "Alexandra" == Alexandra Petlanova Hajkova <ahajkova@redhat.com> writes:
Alexandra> I tested this on aarch64, Fedora 40 and this change causes
Alexandra> gdb.base/bp-cmds-continue-ctrl-c.exp to fail. I can provide
Alexandra> you with the logs if you are interested.
Tom> Sure, that may be helpful.
Tom> I have no idea why this patch would affect that, unless maybe you were
Tom> testing the new mode?
Tom> Hi, I wanted to land this series, but I need to investigate this first.
Tom> Could you send me this log?
Ping.
Tom
next prev parent reply other threads:[~2025-04-22 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 19:19 [PATCH 0/3] Support DWARF 5 .debug_sup section Tom Tromey
2025-03-23 19:20 ` [PATCH 1/3] Remove 'read' call from dwz_file::read_string Tom Tromey
2025-03-24 14:25 ` Alexandra Petlanova Hajkova
2025-03-24 20:30 ` Simon Marchi
2025-03-24 20:52 ` Tom Tromey
2025-03-23 19:20 ` [PATCH 2/3] Handle DWARF 5 separate debug sections Tom Tromey
2025-03-24 15:45 ` Alexandra Petlanova Hajkova
2025-03-24 17:16 ` Tom Tromey
2025-04-03 14:39 ` Tom Tromey
2025-04-22 14:55 ` Tom Tromey [this message]
2025-04-22 15:10 ` Simon Marchi
2025-04-28 11:35 ` Tom de Vries
2025-03-24 20:52 ` Simon Marchi
2025-03-25 13:37 ` Tom Tromey
2025-03-23 19:20 ` [PATCH 3/3] Add "-5" flag to cc-with-tweaks Tom Tromey
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=871ptk8cv4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=ahajkova@redhat.com \
--cc=gdb-patches@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