From: Andrew Cagney <ac131313@cygnus.com>
To: insight@sources.redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: [rfa/patch] string <-> core_addr conversions
Date: Tue, 16 Oct 2001 19:57:00 -0000 [thread overview]
Message-ID: <3BCCF37C.4010403@cygnus.com> (raw)
Hello,
The attached patch changes the way Insight converts from a tcl string to
a CORE_ADDR. Without the patch Insight would use
parse_and_eval_address() when converting an address (in ascii) into a
CORE_ADDR. Unfortunatly, that function, on harvard architectures, does
strange and wonderful things.
You can see the problems if you try to use the memory window to modify
locations.
This code adds a very simple (?) function for converting the tcl integer
directly into a core_addr. It also adds a function to convert a
core_addr to a string (not yet used), I suspect Insight needs an audit
and should ensure that these functions are always used.
Comments? Ok (tcl)? The utils.c change is pretty straightforward.
Andrew
next reply other threads:[~2001-10-16 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 19:57 Andrew Cagney [this message]
2001-10-17 11:22 ` Keith Seitz
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=3BCCF37C.4010403@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).