From: Randolph Chung <randolph@tausq.org>
To: gdb@sources.redhat.com
Subject: gdb for hppa
Date: Mon, 18 Aug 2003 02:51:00 -0000 [thread overview]
Message-ID: <20030818025436.GP21328@tausq.org> (raw)
so, i heard gdb/hppa is looking for some help? :-)
my primary interest is in getting gdb working on hppa-linux, but from
talking to drow, looking at the code and what needs to be done, i
think it'll be worthwhile to merge the palinux code (which is not in
cvs yet) with the hpux stuff in cvs instead of having a separate target.
what is the current status of hppa support? (i'm going to through the
mail archive, but haven't seen very much) is anyone else working on
this? is there a list of "todo" items that i can help with? what do we
need to do to get hppa out of the "obsolete candidate" list?
thanks
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next reply other threads:[~2003-08-18 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 2:51 Randolph Chung [this message]
2003-08-18 3:15 ` MIPS64 problem with symbols Peter Reilley
[not found] ` <mailpost.1061176541.26825@news-sj1-1>
2003-08-18 4:59 ` cgd
2003-08-23 14:48 ` gdb for hppa Joel Brobecker
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=20030818025436.GP21328@tausq.org \
--to=randolph@tausq.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).