Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Marcel Moolenaar <marcel@xcllnt.net>,
	"J. Johnston" <jjohnstn@redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: ia64 tdep patch
Date: Thu, 23 Oct 2003 21:01:00 -0000	[thread overview]
Message-ID: <1031023210049.ZM1243@localhost.localdomain> (raw)
In-Reply-To: Marcel Moolenaar <marcel@xcllnt.net> "Re: RFA: ia64 tdep patch" (Oct 22,  3:02pm)

On Oct 22,  3:02pm, Marcel Moolenaar wrote:

> > They are needed because r32 to r127 are not accessible via the PTRACE 
> > interface. They are accessed via the bsp.  Without flagging them as 
> >  pseudo-registers, the regcache code returns 0 for all these registers.
> 
> It depends. For FreeBSD I added ptrace(2) functions to get and set
> stacked registers that are on the kernel stack. The problem more
> generally is that registers above bspstore (but below bsp) are
> not accessable in memory. I think it's better for gdb to keep the
> distinction between stacked registers on the backing store and
> "dirty" stacked registers. The distinction avoids that gdb makes
> assumptions that are only valid on Linux or even only for the native
> code.

Unfortunately, the assumptions that you mention are already in place.
(And have been in place for quite some time).

> BTW: I have partial support for FreeBSD/ia64. I'll send patches as
> soon as I feel that the backtrace is reliable enough.

Patches will most certainly be welcome.  Do you have an FSF copyright
assignment for GDB yet?  If not, you might want to start working on
the paperwork now...

Kevin


  reply	other threads:[~2003-10-23 21:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 19:58 J. Johnston
2003-10-20 20:13 ` Kevin Buettner
2003-10-20 21:55   ` J. Johnston
2003-10-21 22:22     ` Kevin Buettner
2003-10-21 23:03       ` J. Johnston
2003-10-22 19:38         ` Kevin Buettner
2003-10-22 20:57           ` J. Johnston
2003-10-22 22:01             ` J. Johnston
2003-10-23 16:22               ` J. Johnston
2003-10-23 17:46                 ` Kevin Buettner
2003-10-23 22:07                   ` J. Johnston
2003-10-22 22:03             ` Marcel Moolenaar
2003-10-23 21:01               ` Kevin Buettner [this message]
2003-10-23 23:23                 ` Marcel Moolenaar
2003-10-24  4:30                   ` Kevin Buettner
2003-10-24  5:40                     ` Marcel Moolenaar
2003-10-24  7:08                       ` Kevin Buettner

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=1031023210049.ZM1243@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.com \
    --cc=marcel@xcllnt.net \
    /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