This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: netbsd/x86 and netbsd/walnut gdbserver issues


On Wed, Jun 12, 2002 at 09:20:17PM -0700, Shashi Rao wrote:
> Hi
> 
> I had gdbserver (from 5.1.1) working with netbsd/x86. I was halfway
> toward getting it to work on netbsd/walnut (an IBM powerpc 405GP
> based board. a quirk: the 405GP does not implement FP instructions).
> 
> I modified it to be startable from inetd (so that it would use stdio
> for its "remote socket") and also implemented the "detach"
> remote-serial command (so a ctrl-c at the gdb end would cause a
> ptrace detach of the target on the server side). (I also implemented
> the --attach feature for low-nbsd)
> 
> I'd like to be able to move on to gdb 5.2 (and just got on the
> mailing list) but I notice that netbsd is not a supported target any
> more. I'd like to try and restore the netbsd/x86 target (and also
> provide a netbsd/walnut target) if possible.

Great!

> I dont quite know where to start -- should I just use 
> gdb_5_2-2002-04-29-release as a starting point, and using the
> linux-low stuff as a model, hack on it till things work? Should I be
> doing anything else? Any other pointers? 

Well, I just dumped another large chunk of code into gdbserver, but
it'll probably just make life more confusing (LinuxThreads support). 
But please do take a look at it; patches against current CVS are always
the most useful.  You don't need to implement most of what is there
now, just the little bits described in target.h.  You can probably just
copy lots from linux-low.c; after I see what you copy, I can probably
factor it out into a common file.  I'll be glad to help you along the
way.

> I am not really very familiar with the gdb internals, but now is a
> good time to start!  Also, I'd like to be able to turn in a patch
> if/when I'm successful.

In that case, you should file an FSF copyright disclaimer.  I've
attached the request form.  You may also need an employer disclaimer.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer
(The following assumes that you want to assign past *and future*
changes to these programs.  If you want (or need) to restrict your
copyright assignment to changes you have already made, then just
delete the words "AND FUTURE" below.

The "past changes only" form would allow you to contribute minor
revisions of your previous changes, but otherwise would not cover
future work. - Brian Youmans, FSF)

--------------------------------------------------------------------
Please email the following information to fsf-records@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]


[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]








Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]