Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ben Harris <bjh21@netbsd.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: <Richard.Earnshaw@arm.com>, <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: Thu, 25 Oct 2001 12:51:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.33.0110252036560.6626-100000@virgo.cus.cam.ac.uk> (raw)
In-Reply-To: <3BD73EF2.4050209@cygnus.com>

On Wed, 24 Oct 2001, Andrew Cagney wrote:

> If this is true, can I suggest to the Arm maintainers that this be
> considered.

I'd suggest that, for consistency with the other NetBSD ports,
armbsd-nat.c be renamed armnbsd-nat.c

> Then BenH can apply fixes to it (always easier and less
> likely to have assignment problems) then new code.  (I understand, third
> hand this is kind of BenH's plan already).

This is my plan, yes, to the extent that I've already removed Mark's code
from our in-tree GDB 5.0 and replaced it with Richard's.

-- 
Ben Harris                                                   <bjh21@netbsd.org>
Portmaster, NetBSD/arm26               <URL: http://www.netbsd.org/Ports/arm26/ >


  reply	other threads:[~2001-10-25 12:51 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
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 [this message]
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=Pine.SOL.4.33.0110252036560.6626-100000@virgo.cus.cam.ac.uk \
    --to=bjh21@netbsd.org \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@cygnus.com \
    --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