From: Alexey Lapshin <alexey.lapshin@espressif.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"tom@tromey.com" <tom@tromey.com>
Cc: Alexey Gerenkov <alexey.gerenkov@espressif.com>,
Anton Maklakov <anton.maklakov@espressif.com>,
Ivan Grokhotkov <ivan@espressif.com>,
"jcmvbkbc@gmail.com" <jcmvbkbc@gmail.com>
Subject: [PATCH v3] gdb: xtensa: fix registers supply if they not present
Date: Wed, 3 Apr 2024 14:49:30 +0000 [thread overview]
Message-ID: <7d4ffc9a33ad7a7acea80c6bc3fabef57941fb1c.camel@espressif.com> (raw)
In-Reply-To: <9f7a82d385ccbc4c249ff7ecebff24fa42ebb149.camel@espressif.com>
Ping
next prev parent reply other threads:[~2024-04-03 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 6:28 [PATCH v2] gdb: xtensa: don't supply registers if they are " Alexey Lapshin
2023-02-24 19:55 ` Tom Tromey
2023-05-16 4:17 ` [PATCH v3] gdb: xtensa: fix registers supply if they " Alexey Lapshin
2024-04-03 14:49 ` Alexey Lapshin [this message]
2024-04-09 17:59 ` John Baldwin
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=7d4ffc9a33ad7a7acea80c6bc3fabef57941fb1c.camel@espressif.com \
--to=alexey.lapshin@espressif.com \
--cc=alexey.gerenkov@espressif.com \
--cc=anton.maklakov@espressif.com \
--cc=gdb-patches@sourceware.org \
--cc=ivan@espressif.com \
--cc=jcmvbkbc@gmail.com \
--cc=tom@tromey.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).