From: Aaron Merey <amerey@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: luis.machado@arm.com, aburgess@redhat.com,
thiago.bauermann@linaro.org, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4 v8] gdb: Buffer output streams during events that might download debuginfo
Date: Fri, 19 Jan 2024 14:52:30 -0500 [thread overview]
Message-ID: <CAJDtP-ShQP3RWyDMOq5_wouR8Gwyy+EcTBEjHPnzb1Gfqbv-Gw@mail.gmail.com> (raw)
In-Reply-To: <6fb49b9c-691a-4a65-9af5-844b31a534af@suse.de>
Hi Tom,
On Fri, Jan 19, 2024 at 2:33 PM Tom de Vries <tdevries@suse.de> wrote:
>
> what you're describing here sounds like exception slicing.
>
> The easiest way to fix this is by rethrowing using "throw" without argument.
>
> See this ( https://en.cppreference.com/w/cpp/language/throw ):
> ...
> When rethrowing exceptions, the second form must be used to avoid object
> slicing in the (typical) case where exception objects use inheritance: ...
Gotcha, thanks for clarifying. I wasn't aware of the second form of throw.
Aaron
next prev parent reply other threads:[~2024-01-19 19:53 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
2024-01-19 17:13 ` Aaron Merey
2024-01-19 19:34 ` Tom de Vries
2024-01-19 19:52 ` Aaron Merey [this message]
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=CAJDtP-ShQP3RWyDMOq5_wouR8Gwyy+EcTBEjHPnzb1Gfqbv-Gw@mail.gmail.com \
--to=amerey@redhat.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=tdevries@suse.de \
--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