From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Randolph Chung" <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [hppa patch] Fix register definitions for hppa
Date: Sat, 04 Aug 2007 16:35:00 -0000 [thread overview]
Message-ID: <119aab440708040935l71bba985uf7a782252a760d3@mail.gmail.com> (raw)
In-Reply-To: <20070803201219.GC32611@tausq.org>
On 8/3/07, Randolph Chung <randolph@tausq.org> wrote:
> Remember that gdb is reading the cr27 of the debuggee, not of itself, so
> __set_cr27 is irrelevant.
Is it usefull to be able to adjust the inferior's thread register?
> From the architecture point of view, CR26 and CR27 are only readable
> from userspace, so gdb should not enable somebody to set them from
> inside gdb.
Would it be usefull to adjust the thread register when debugging glibc?
Cheers,
Carlos.
next prev parent reply other threads:[~2007-08-04 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 17:06 Randolph Chung
2007-08-03 17:11 ` Daniel Jacobowitz
2007-08-03 18:42 ` [parisc-linux] " Carlos O'Donell
2007-08-03 20:12 ` Randolph Chung
2007-08-04 16:35 ` Carlos O'Donell [this message]
2007-08-04 17:02 ` 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=119aab440708040935l71bba985uf7a782252a760d3@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=gdb-patches@sources.redhat.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
/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