Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@lecomber.net>
To: gdb@sources.redhat.com
Subject: ia64 register cache (not!)
Date: Thu, 09 Feb 2006 12:30:00 -0000	[thread overview]
Message-ID: <20060209123032.GA10585@streamline-computing.com> (raw)



Dear all,

The ia64 (on suse9.3) of gdb seems to not use the PTRACE_GETREGS, but 
goes fetching each register in turn.  This seems a bit crazy, and the 
source of some very slow behaviour (given the number of ia64 registers!).

There seems to be some source that was intended to handle the GETREGS 
but is probably not being called (ia64-linux-nat.c).

When I debug, gdb is definitely calling the fetch_inferior_registers
defined inside infptrace.c (btw, this is GDB from June'05, but it seems 
that the excessive ptrace behaviour is the same in most recent CVS too)..  

Anyone have an idea why it's this way?  I've watched how gdb handles the
i386 version -- going off into fetch_inferior_registers in i386-linux-nat.c.

d.


             reply	other threads:[~2006-02-09 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 12:30 David Lecomber [this message]
2006-02-09 14:16 ` M.M. Kettenis
2006-02-09 14:19   ` Daniel Jacobowitz
2006-02-09 14:40     ` David Lecomber

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=20060209123032.GA10585@streamline-computing.com \
    --to=david@lecomber.net \
    --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