From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb@sources.redhat.com
Subject: FYI: mips-linux port status
Date: Tue, 03 Jul 2001 13:03:00 -0000 [thread overview]
Message-ID: <20010703130228.A5249@nevyn.them.org> (raw)
After some interesting toolchain fiddling, and a little help from H.J. Lu
with more toolchain work, I've got the port in what I consider acceptable
shape. I'm down to under fifty FAILs now, and the largest portion of my
patches to other areas of GDB are merged in. There's a few yet to go,
though.
The known issues are:
- need to implement sigtramp functions; they're just FIXMEs still
- once you stop inside a shared library, you can't backtrace out of it. I
believe I know mostly what's going wrong; I'll get back to this in a
little while.
- copyright. I can't get a response from David Miller as to whether or
not he filed the assignment paperwork for the original work he did on
this code. While very little of what he did is left, and decreasing
every day, I believe we may still need an assignment. Does anyone have
a more effective way to reach him than email, or know whether that
assignment was filed?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2001-07-03 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 13:03 Daniel Jacobowitz [this message]
2001-07-03 23:06 ` Andreas Jaeger
2001-07-04 8:37 ` Andrew Cagney
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=20010703130228.A5249@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--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