From: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v1] gdb/DAP Fix disassemble bug
Date: Tue, 27 Jun 2023 17:32:53 +0200 [thread overview]
Message-ID: <55387162-b26d-01b8-105c-11bf432a1f3c@gmail.com> (raw)
In-Reply-To: <2c7beaa5-a45c-b97a-a4d8-44a092a00471@gmail.com>
I've got a working "backwards disassemble" patch, coming soon.
On 6/27/23 00:11, Simon Farre wrote:
> Also, I don't know what design GDB has, but this kind of information
> is probably knowable by utilizing DWARF. Just guessing here, but it
> seems like if one were to use the line number program in dwarf, being
> able to "disassemble backwards" should be fairly easy. That kind of
> would have to require that the current design is suitable for that and
> the little I've looked at it I don't think this is the case,
> unfortunately. I'll update the patch by just returning "invalid
> values" prior to the "current pc".
prev parent reply other threads:[~2023-06-27 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 16:16 Simon Farre via Gdb-patches
2023-06-26 18:34 ` Tom Tromey
2023-06-26 22:00 ` Simon Farre via Gdb-patches
2023-06-26 22:11 ` Simon Farre via Gdb-patches
2023-06-27 15:32 ` Simon Farre via Gdb-patches [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=55387162-b26d-01b8-105c-11bf432a1f3c@gmail.com \
--to=gdb-patches@sourceware.org \
--cc=simon.farre.cx@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