public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kev@primenet.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA-64 Linux TODO list
Date: Tue, 09 Jan 2001 21:25:14 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205900@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205896@msgid-missing>

On Jan 9, 12:47pm, Don Dugger wrote:

> I'm willing to take on the taks of maintaining this list.  For now
> I'll put David's name next to the `kernel unaligned handler' and
> I'm willing to look into the `strace' issues.  If anyone else is
> willing to take on anything let me know and I'll add your name.
> I think it would be a good idea to have a responsible person for
> each item if possible.

Put me down for gdb.

> >  - gdb
> >     - NaT bits don't seem to work properly?
> >     - coredump support still broken?

I have a couple of other items to add to this list of things which
isn't working in gdb.

1) Calling inferior functions no longer works.  (At least it didn't in
   the recent Red Hat release.  I'm rebuilding gdb now with the
   TurboLinux release to check it there.) I've done some investigation
   of this problem and it looks to me like the RSE backing store is
   changing under us (gdb that is) when bsp is changed.

2) Hardware watchpoints no longer work.  Again, the value returned
   by the kernel looks suspect.  There appear to be a couple of bits
   that were reset...

In general, the state of gdb isn't as good right now as it used to
be.  There was a time when I was seeing only between 20-30 test
suite failures.  The number is now over 700.

Kevin


  parent reply	other threads:[~2001-01-09 21:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 19:23 [Linux-ia64] IA-64 Linux TODO list David Mosberger
2001-01-09 19:47 ` Don Dugger
2001-01-09 20:05 ` Uros Prestor
2001-01-09 20:32 ` Ahna, Christopher J
2001-01-09 21:25 ` Kevin Buettner [this message]
2001-01-09 21:44 ` David Mosberger
2001-01-10 21:51 ` Don Dugger
2001-01-11 17:29 ` Jes Sorensen
2001-01-25  0:19 ` Johannes Erdfelt

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=marc-linux-ia64-105590678205900@msgid-missing \
    --to=kev@primenet.com \
    --cc=linux-ia64@vger.kernel.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