From: "Frank Ch. Eigler" <fche@redhat.com>
To: sid@sources.redhat.com
Subject: Enabling gdb-interface Z packet by default
Date: Mon, 02 Apr 2001 12:39:00 -0000 [thread overview]
Message-ID: <20010402153950.E13135@redhat.com> (raw)
Hi -
I would like to commit the following patch to sid/bsp/configrun-sid.in,
intended to by default support the gdb remote protocol "Z" packet. The
purpose of this change is to add some resilience against unilateral
changes in gdb land to designated breakpoint instructions.
Instead of overwriting instruction memory, gdb uses the Z packet to
give us a PC value, which in turn is translated to a sid triggerpoint
on the PC register. This has the drawback that it slows down the
simulation, and requires gdb to supply a proper PC value (compensated
for word-based addressing, harvard architectures, etc.). Still, methinks
being able to function despite some gdb changes is worthwhile.
Any comments?
- FChE
2001-04-02 Frank Ch. Eigler <fche@redhat.com>
* configrun-sid.in (enable_z_packet): Change default to "true".
Index: configrun-sid.in
===================================================================
RCS file: /cvs/cvsfiles/devo/sid/bsp/configrun-sid.in,v
retrieving revision 1.55
diff -u -r1.55 configrun-sid.in
--- configrun-sid.in 2001/03/27 16:40:12 1.55
+++ configrun-sid.in 2001/04/02 19:09:36
@@ -402,7 +402,7 @@
&sidconf_new("sw-profile-gprof", "gprof") . "\n";
}
-$enable_z_packet = "false";
+$enable_z_packet = "true";
$second_section = "# second section
# settings
set cpu step-insn-count $cpu_insn_count
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6yNWGVZbdDOm/ZT0RAg7WAJ9bF+ywdpE5FkMimqoek9HMuMeoXgCghrbN
Ipb7hG65gLxZaJRnfcDfsgM=
=iPtD
-----END PGP SIGNATURE-----
next reply other threads:[~2001-04-02 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 12:39 Frank Ch. Eigler [this message]
2001-04-02 14:44 ` Ben Elliston
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=20010402153950.E13135@redhat.com \
--to=fche@redhat.com \
--cc=sid@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).