Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Ben Harris <bjh21@netbsd.org>,
	gdb-patches@sourceware.cygnus.com, Jim blandy <jimb@cygnus.com>,
	Todd Vierling <tv@wasabisystems.com>,
	Richard.Earnshaw@arm.com
Subject: Re: Fix stack backtraces on 26-bit ARM
Date: Mon, 22 Oct 2001 04:04:00 -0000	[thread overview]
Message-ID: <200110221104.MAA06894@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: <200110221019.LAA03730@cam-mail2.cambridge.arm.com>

> Hmm, I have the bones of a completely clean NetBSD/arm port.  It isn't 
> complete, but it was written without reference to the existing NetBSD code.
> 

Ok, attached is most of the code.  There's one more patch, which I'll send
separately, that allows ARM targets to be single-stepped when there is no
kernel/hw support for single stepping.

R.

<date> Richard Earnshaw <rearnsha@arm.com>

	* config/arm/nbsd.mh config/arm/nbsd.mt config/arm/tm-nbsd.h
	config/arm/nm-nbsd.h config/arm/xm-nbsd.h: New files.
	* armbsd-nat.c: New file.
	* Makefile.in: Build it.
	* configure.host configure.tgt: Support NetBSD/arm.



  reply	other threads:[~2001-10-22  4:04 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 [this message]
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=200110221104.MAA06894@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=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