From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Consistent format for memory addresses
Date: Wed, 25 May 2005 04:12:00 -0000 [thread overview]
Message-ID: <17043.64325.889868.708579@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050525033745.GA25868@nevyn.them.org>
> I have no objection - but is it really that hard to treat it as a
> number?
I see what you're saying now. I take the current address from "info frame" and
then search for it in the output of disassemble. This lets me place an arrow
on the appropriate line in the "disassembly window". That means I have to
treat the address as a string which presents a problem when the different
commands use different formats.
Nick
next prev parent reply other threads:[~2005-05-25 4:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 3:18 Nick Roberts
2005-05-25 3:37 ` Daniel Jacobowitz
2005-05-25 3:51 ` Nick Roberts
2005-05-25 18:00 ` Eli Zaretskii
2005-05-25 21:10 ` Nick Roberts
2005-05-25 21:28 ` Daniel Jacobowitz
2005-05-25 23:11 ` Nick Roberts
2005-05-26 3:39 ` Eli Zaretskii
2005-05-26 3:46 ` Daniel Jacobowitz
2005-05-26 4:12 ` Nick Roberts
2005-05-25 4:12 ` Nick Roberts [this message]
2005-05-25 5:27 ` M.M. Kettenis
2005-05-25 5:48 ` Nick Roberts
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=17043.64325.889868.708579@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--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