Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Ben Harris <bjh21@netbsd.org>
Cc: gdb-patches@sourceware.cygnus.com, Jim blandy <jimb@cygnus.com>,
	Todd Vierling <tv@wasabisystems.com>
Subject: Re: Fix stack backtraces on 26-bit ARM
Date: Sun, 21 Oct 2001 09:12:00 -0000	[thread overview]
Message-ID: <3BD2F3E0.2030603@cygnus.com> (raw)
In-Reply-To: <Pine.SOL.4.33.0110211150570.14053-100000@virgo.cus.cam.ac.uk>

> On Sat, 20 Oct 2001, Andrew Cagney wrote:
> 
> 
>> Hmm, this could get interesting.  A NetBSD/arm port of GDB would
>> certainly help improve the quality of the Arm GDB target.  Your
>> contribution are going to be most welcome.  Problem is, I can't find a
>> copyright assignment for you (you'll get a separate e-mail about this).
>> Can you please clarify your assignment status?  Not having an
>> assignment can make things, er, interesting.  At present your submitting
>> small simple bugs that can be described in simple english.
> 
> 
> I've signed assignments for GCC and Binutils.  I'm happy to sign one for
> GDB as well.  I haven't worked out quite who wrote our existing ARM GDB
> stuff: it was checked in by Todd Vierling, but I think the work was mostly
> done by Mark Brinicombe.

Yes, please get an assignment.  It makes everyones life soooo much easier.

If you're not sure where the code came from and/or it isn't clear that 
the original contributors have an assignment then you'll need to 
``ignore'' it.  Most recent *BSD contributors have ended up abandoning 
their old branch, instead starting anew.

Having said that, the approach you appear to be taking looks to be the 
right one - identify individual bugs and get them submitted/fixed.

>> The other thing to know is that patches should be against the current
>> trunk rather than the last release.  5.0 is just so old ...
> 
> 
> Unfortunately, 5.0 is what NetBSD is currently working towards using, so
> all my patches are likely to start life there.  I'll do what I can to
> ensure they're still relevant to the trunk, though.

Hmm, something additional to note, GDB 5.1-branch and current both work 
on many more NetBSD systems than 5.0.  You man want to consider getting 
current working first.

good luck!
Andrew



  reply	other threads:[~2001-10-21  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SOL.4.33.0110201735080.16292-100000@virgo.cus.cam.ac.uk>
2001-10-20 11:05 ` Andrew Cagney
2001-10-21  6:22   ` Ben Harris
2001-10-21  9:12     ` Andrew Cagney [this message]
2001-10-22  3:20       ` Richard Earnshaw
2001-10-22  4:04         ` Richard Earnshaw
2001-10-22  4:18           ` [patch]: Software single-stepping on ARMs Richard Earnshaw
2001-12-17  8:40             ` Fernando Nasser
2001-12-17  9:04             ` Fernando Nasser
2001-10-24 15:22           ` Fix stack backtraces on 26-bit ARM Andrew Cagney
2001-10-25 12:51             ` Ben Harris
2001-12-17  8:34             ` Fernando Nasser

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=3BD2F3E0.2030603@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=bjh21@netbsd.org \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jimb@cygnus.com \
    --cc=tv@wasabisystems.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