From: Vasili Burdo <vasili.burdo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] TUI disassembly window improvemenmt
Date: Wed, 9 Jun 2021 16:16:08 +0300 [thread overview]
Message-ID: <CANacp63qrmvnj8WSND7Cxo6rvK_CUXm9eqP+xaxZ-pf4XpMg7Q@mail.gmail.com> (raw)
In-Reply-To: <83zgvzcho1.fsf@gnu.org>
Eli, please take look at screenshots I posted: https://imgur.com/a/GlkVXGi
They show disassembly starting from the same address.
>if some other function is referenced in the disassembly, it will now be invisible, right?
No. Only "address" part for disassembly line is changed. "insn" part
which contains references is intact.
>IOW, you seem to assume that any function names mentioned in the disassembly are always the name of the current function
I didn't make any assumptions of this kind.
ср, 9 июн. 2021 г. в 16:05, Eli Zaretskii <eliz@gnu.org>:
>
> > From: Vasili Burdo <vasili.burdo@gmail.com>
> > Date: Wed, 9 Jun 2021 15:56:38 +0300
> > Cc: gdb-patches@sourceware.org
> >
> > > Shouldn't this be optional behavior? Not everyone disassembles only
> > > C++ code.
> > This patch does not limit disassembly view in any way.
> > - The current function name moved from disassembly line to window header
> > - Offset from function start still present in disassembly line
> > - Function start is marked by function name label.
>
> But AFAIU only the current function's name is visible; if some other
> function is referenced in the disassembly, it will now be invisible,
> right?
>
> IOW, you seem to assume that any function names mentioned in the
> disassembly are always the name of the current function, but is that
> an assumption that is always correct?
next prev parent reply other threads:[~2021-06-09 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 16:16 Vasili Burdo
2021-06-08 16:21 ` Simon Marchi
2021-06-09 12:33 ` Eli Zaretskii
2021-06-09 12:56 ` Vasili Burdo
2021-06-09 13:05 ` Eli Zaretskii
2021-06-09 13:16 ` Vasili Burdo [this message]
2021-06-09 13:43 ` Eli Zaretskii
[not found] ` <CANacp62RQ4eTK+YYcukgxh=MzmAAdvK5AYTPe6RZubhejMePeg@mail.gmail.com>
2021-06-09 16:02 ` Fwd: " Vasili Burdo
2021-06-09 17:14 ` Eli Zaretskii
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=CANacp63qrmvnj8WSND7Cxo6rvK_CUXm9eqP+xaxZ-pf4XpMg7Q@mail.gmail.com \
--to=vasili.burdo@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).