From: Tom Tromey <tom@tromey.com>
To: Lancelot Six via Gdb-patches <gdb-patches@sourceware.org>
Cc: Lancelot Six <lancelot.six@amd.com>, <lsix@lancelotsix.com>
Subject: Re: [PATCH] gdb: fix build failure in amd-dbgapi-target.c
Date: Wed, 23 Aug 2023 11:42:28 -0600 [thread overview]
Message-ID: <87jztlvenv.fsf@tromey.com> (raw)
In-Reply-To: <20230823145902.297879-1-lancelot.six@amd.com> (Lancelot Six via Gdb-patches's message of "Wed, 23 Aug 2023 14:59:02 +0000")
>>>>> "Lancelot" == Lancelot Six via Gdb-patches <gdb-patches@sourceware.org> writes:
Lancelot> Since b080fe54fb3 "gdb: add inferior-specific breakpoints", the
Lancelot> breakpoint class has an "inferior" member used to handle
Lancelot> inferior-specific breakpoints. This creates a compilation error
Lancelot> in amd_dbgapi_target_breakpoint::check_status which declares a local
Lancelot> variable "inferior *inf".
Lancelot> Fix this by using "struct inferior *inf" instead.
This kind of thing can go in as obvious.
Tom
prev parent reply other threads:[~2023-08-23 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:59 Lancelot Six
2023-08-23 15:23 ` Pedro Alves
2023-08-23 15:45 ` Six, Lancelot
2023-08-23 17:42 ` Tom Tromey [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=87jztlvenv.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.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).