From: Simon Marchi <simark@simark.ca>
To: "LEROY Christophe" <christophe.leroy@csgroup.eu>,
"Cédric Le Goater" <clg@kaod.org>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"dbarboza@redhat.com" <dbarboza@redhat.com>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>,
"gdb@sourceware.org" <gdb@sourceware.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Greg Kurz" <groug@kaod.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@csgraf.de>,
qemu-ppc <qemu-ppc@nongnu.org>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: Deprecate the ppc405 boards in QEMU? (was: [PATCH v3 4/7] MAINTAINERS: Orphan obscure ppc platforms)
Date: Wed, 20 Oct 2021 11:04:07 -0400 [thread overview]
Message-ID: <0d1e13a2-1c16-6c6d-3f7e-87024ed2a8aa@simark.ca> (raw)
In-Reply-To: <5263c819-b13c-f48a-d720-15b085537070@csgroup.eu>
On 2021-10-20 9:16 a.m., LEROY Christophe wrote:
> And GDB 11.1 coredumps while reading vmlinux's symbols
>
> Hopefully I'll find a GDB version between 7.8 and 11 that works.
That's not cool. Could you file a bug for it? If you could share your
vmlinux executable (or steps to re-create it, with details about compiler
version and all), that would be very helpful.
Thanks,
Simon
next prev parent reply other threads:[~2021-10-20 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210927044808.73391-1-david@gibson.dropbear.id.au>
[not found] ` <20210927044808.73391-5-david@gibson.dropbear.id.au>
[not found] ` <18fa56ee-956e-ee2f-9270-82aa96dfde09@redhat.com>
[not found] ` <df767942-be5f-c920-2924-a5221e9db2b3@csgroup.eu>
[not found] ` <40cdb137-60c9-43fd-7b48-4858cbd9307c@redhat.com>
[not found] ` <CAFEAcA82L5JiHXUmc0vt7EgiiyrYHyJ+qQ7pFHp+CsvJCPyKqA@mail.gmail.com>
[not found] ` <6c2ff4e6-4bf4-d310-5e26-c8d2741177bc@redhat.com>
[not found] ` <42e5a8c2-b8fa-b9e2-71f1-c8e5cd7f5cef@csgroup.eu>
[not found] ` <1397f18f-f187-6f48-ed6c-13c0b77abed9@redhat.com>
[not found] ` <YVug7l8LWl3e+DN5@yekko>
[not found] ` <9aeb7010-0a17-864a-cfac-ea5d90356085@csgroup.eu>
[not found] ` <f0871969-190a-d15e-50d8-e6c1b1043652@ozlabs.ru>
[not found] ` <5e4f78ce-1508-5689-ec29-79edad0c824e@kaod.org>
[not found] ` <491d6265-3785-b11-b7f0-621a3d2823@eik.bme.hu>
[not found] ` <b9f27c1b-1162-b178-9333-89c0dd707c12@redhat.com>
[not found] ` <103e098a-a8ac-a22a-8aad-3df7d8cde148@amsat.org>
[not found] ` <939f2d12-38f6-4ab0-b688-384136d1d9c@eik.bme.hu>
[not found] ` <4e07823e-7162-525a-4a61-9bed63e85d58@kaod.org>
2021-10-20 13:16 ` LEROY Christophe
2021-10-20 15:04 ` Simon Marchi [this message]
2021-10-28 12:24 ` Luis Machado
2021-10-28 17:27 ` Christophe Leroy
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=0d1e13a2-1c16-6c6d-3f7e-87024ed2a8aa@simark.ca \
--to=simark@simark.ca \
--cc=agraf@csgraf.de \
--cc=aik@ozlabs.ru \
--cc=balaton@eik.bme.hu \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=dbarboza@redhat.com \
--cc=f4bug@amsat.org \
--cc=gdb@sourceware.org \
--cc=groug@kaod.org \
--cc=hpoussin@reactos.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.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).