From: Luis Machado <luis.machado@arm.com>
To: Aaron Merey <amerey@redhat.com>, Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org, thiago.bauermann@linaro.org
Subject: Re: [PATCH 1/4 v8] gdb: Buffer output streams during events that might download debuginfo
Date: Fri, 19 Jan 2024 14:35:31 +0000 [thread overview]
Message-ID: <35826cb5-1ff6-4101-9105-ffb9512e7b44@arm.com> (raw)
In-Reply-To: <CAJDtP-SHyFVTOfYieRzFqLisuHGOu-QodmZOiEdrAjauUfYg0Q@mail.gmail.com>
Hi Aaron,
On 1/19/24 05:28, Aaron Merey wrote:
> On Thu, Jan 18, 2024 at 6:22 AM Andrew Burgess <aburgess@redhat.com> wrote:
>>
>> So, given nobody who knows the I/O stuff better has commented, I propose
>> that, with the fixes I've pointed out above:
>>
>> Approved-By: Andrew Burgess <aburgess@redhat.com>
>
> Thanks Andrew. The issues you pointed out were fixed and the patch
> was pushed as commit 519d63439.
>
> Aaron
>
I bisected a number of failures in gdb.dwarf2/dw2-dir-file-name.exp to commit 519d634396592c5698add4a327468e6e6920576e.
In particular, my testing was done on aarch64-linux (Ubuntu 20.04).
next prev parent reply other threads:[~2024-01-19 14:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 15:48 [PATCH 0/4] On-demand debuginfo downloading Aaron Merey
2024-01-17 15:48 ` [PATCH 1/4 v8] gdb: Buffer output streams during events that might download debuginfo Aaron Merey
2024-01-18 11:22 ` Andrew Burgess
2024-01-19 5:28 ` Aaron Merey
2024-01-19 14:35 ` Luis Machado [this message]
2024-01-19 17:13 ` Aaron Merey
2024-01-19 19:34 ` Tom de Vries
2024-01-19 19:52 ` Aaron Merey
2024-01-17 15:48 ` [PATCH 2/4 v3] gdb/progspace: Add reverse safe iterator Aaron Merey
2024-01-18 12:02 ` Andrew Burgess
2024-01-19 5:09 ` Aaron Merey
2024-02-07 21:24 ` [PING][PATCH " Aaron Merey
2024-02-22 22:22 ` [PING*2][PATCH " Aaron Merey
2024-03-01 0:09 ` [PING*3][PATCH " Aaron Merey
2024-03-12 22:14 ` Aaron Merey
2024-01-17 15:48 ` [PATCH 3/4 v5] gdb/debuginfod: Support on-demand debuginfo downloading Aaron Merey
2024-01-18 15:34 ` Andrew Burgess
2024-01-19 5:12 ` Aaron Merey
2024-02-07 21:25 ` [PING][PATCH " Aaron Merey
2024-02-22 22:23 ` [PING*2][PATCH " Aaron Merey
2024-03-01 0:09 ` [PING*3][PATCH " Aaron Merey
2024-03-12 22:15 ` Aaron Merey
2024-03-27 10:58 ` [PATCH " Andrew Burgess
2024-03-27 23:56 ` Aaron Merey
2024-01-17 15:48 ` [PATCH 4/4 v6] gdb/debuginfod: Add .debug_line downloading Aaron Merey
2024-02-07 21:25 ` [PING][PATCH " Aaron Merey
2024-02-22 22:23 ` [PING*2][PATCH " Aaron Merey
2024-03-01 0:10 ` [PING*3][PATCH " Aaron Merey
2024-03-12 22:15 ` Aaron Merey
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=35826cb5-1ff6-4101-9105-ffb9512e7b44@arm.com \
--to=luis.machado@arm.com \
--cc=aburgess@redhat.com \
--cc=amerey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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