Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>,
	Jim Blandy <jimb@zenia.red-bean.com>,
	gdb@sources.redhat.com
Subject: Re: HP catchpoint code
Date: Wed, 14 Aug 2002 09:21:00 -0000	[thread overview]
Message-ID: <20020814161918.GA23968@systemhalted> (raw)
In-Reply-To: <20020814141348.GA20524@nevyn.them.org>

> 
> Absolutely.  It's gotten (started?) very crufty, and _no one_ has been
> willing to maintain it.  I know ye HPPA/Linux folks have your own port,
> and so far not a soul has been willing to contribute it to GDB - I
> don't know who can, I sure didn't write it, I just include it in the
> Debian packages to make Randolph stop nagging me :)
> 
> More to the point, though - if someone steps forward to do some
> long-needed work on PARISC, that can stay, but HP/UX support is what I
> really want to leave (or be updated).
> 

I can't plead ignorance on the issue since Matthew Wilcox mentioned 
that GDB wanted to drop PARISC support... and the main reason I'm on this
list, and others, is to keep a finger on the pulse of PARISC specific 
problems across the board from binutils/gcc/glibc/gdb.

I'll step forward to do PARISC support for GDB.
These may be my famous last words ;)

AFAIK the issues revolve around some final FSF paperwork that Alan Modra
needs to complete to get the debian .dpatch's accepted upstream? All of 
our modifications to gdb are in the debian package as patches. We do have
a gdb cvs tree, but that is based on Randolph's 5.1 merge. I will get 
this up to date as soon as possible.

As for new development, and moving forward with PARISC (HP/UX support?)
that will take my time, research and development. Not to mention more
gdb source digging... 

c.


  reply	other threads:[~2002-08-14 16:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12  8:33 Daniel Jacobowitz
2002-08-13 13:49 ` Jim Blandy
2002-08-13 14:41   ` Daniel Jacobowitz
2002-08-13 14:59     ` Andrew Cagney
2002-08-14  7:06       ` Carlos O'Donell
2002-08-14  7:13         ` Daniel Jacobowitz
2002-08-14  9:21           ` Carlos O'Donell [this message]
2002-08-15 18:53             ` Andrew Cagney
2002-08-16  5:46               ` Carlos O'Donell
2002-10-18 15:16       ` Daniel Jacobowitz
2002-10-21 12:08         ` Andrew Cagney
2002-10-21  8:33           ` Daniel Jacobowitz
2002-10-21 12:08             ` Andrew Cagney
2002-10-21 12:13               ` Daniel Jacobowitz
2002-10-22  8:17                 ` Andrew Cagney
2002-11-07 15:24             ` Andrew Cagney
2002-11-07 19:21               ` 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=20020814161918.GA23968@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=ac131313@ges.redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@zenia.red-bean.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