From: James Ingham <jingham@cygnus.com>
To: tromey@cygnus.com
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: assembly display -vs- popups
Date: Mon, 17 Apr 2000 12:58:00 -0000 [thread overview]
Message-ID: <14587.28052.611834.422597@leda.cygnus.com> (raw)
In-Reply-To: <87bt38h5kp.fsf@cygnus.com>
Tom,
> While debugging my gcj-generated stubs I always use the assembly view,
> because there isn't any source corresponding to the code I'm
> debugging.
>
> In assembly mode I see code like this (on my x86 box):
>
> - 0x403077ca <simple_int.nat(int)+42>: mov %eax,0xfffffff8(%ebp)
>
> If I highlight "%ebp", I'd like it to display the value of the
> register in the balloon. Unfortunately, it does not, because "%ebp"
> is not valid gdb syntax for getting the register value.
>
> A hack would be to do `s/%/$/' to the expression in assembly mode.
This makes me nervous. It is not guaranteed to work everywhere. Not
everybody uses % for registers in their standard dissassembler. On
MIPS a $ is used. Who knows what some other architecture might
choose... More importantly, there is no guarantee that replacing the
% with $ is benign...
>
> This is bad because ideally I'd like to be able to highlight
> 0xfffffff8(%ebp) and have it do the right thing. Maybe assembly needs
> a different expression evaluator, making this a more general gdb
> problem?
I think this is right; Insight just feeds whatever you highlight to
evaluate_expression... The problem is that gdb doesn't seem to
evaluate assembly expressions in the format used by the disassembler,
which certainly seems wrong to me.
Jim
prev parent reply other threads:[~2000-04-17 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-17 12:46 Tom Tromey
2000-04-17 12:58 ` James Ingham [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=14587.28052.611834.422597@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=tromey@cygnus.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).