From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: source with inlined assembly
Date: Sat, 28 Jun 2003 15:20:00 -0000 [thread overview]
Message-ID: <20030628150159.GA2774@white> (raw)
Hi,
I am investigating the best way to show the user assembly code via my
front end called cgdb. It appears that there is a disassemble function
that will get the assembly code.
Is there any way to nicely show to the user the source with the assembly
inlined between the source lines? Can I ask gdb for the assembly for 1
source line of code? Then can I ask it the assembly for every source
line of code in a file?
What is the mechanism for doing this with a front end? I really want to
stay away from parsing the output of the disassemble command to try to
guess which assembly lines go with the source code.
Also, if up till now there is only a disassemble function and this
doesn't supply a front end with what I am asking for, does this seem
like a good feature to add to the mi command set?
Thanks for your time,
Bob Rossi
next reply other threads:[~2003-06-28 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 15:20 Bob Rossi [this message]
2003-06-28 15:21 ` Daniel Jacobowitz
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=20030628150159.GA2774@white \
--to=bob@brasko.net \
--cc=gdb@sources.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