From: "Larry McCourry" <lmccourry@CHARTER.NET>
To: "Grant Edwards" <grante@visi.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: ARM
Date: Thu, 23 Oct 2003 18:50:00 -0000 [thread overview]
Message-ID: <000c01c39995$77fd1f40$6401a8c0@betsy> (raw)
In-Reply-To: <20031023183633.GA21462@grante.dsl.visi.com>
Does the following not mean that it doesn't work?
from
http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/src/gdb/PROBLEMS?con
tent-type=text/x-cvsweb-markup&cvsroot=src
...
arm-*-*
GDB's ARM target, in 6.0, has not been updated to use the new frame
mechanism.
Fortunatly the ARM target, in the GDB's mainline sources, has been
updated so people encountering problems should consider downloading a
more current GDB (http://www.gnu.org/software/gdb/current).
....
Anyway, gdb-6.0 doesn't work for me. I do the following on win2k and cygwin,
talking to an AT91EB40 board with the Angel debug monitor running:
1. arm-elf-gdb
2. set remotebaud 9600
3. target rdi com1
gdb hangs
In hyperterm I can see angel sending "valid" stuff out the serial port when
I press reset on the board. Bincom-loaded programs work on the board.
Larry McCourry
----- Original Message -----
From: "Grant Edwards" <grante@visi.com>
To: "Larry McCourry" <lmccourry@charter.net>
Cc: <gdb@sources.redhat.com>
Sent: Thursday, October 23, 2003 2:36 PM
Subject: Re: ARM
> On Thu, Oct 23, 2003 at 02:24:19PM -0400, Larry McCourry wrote:
>
> > When will the ARM processor be supported in gdb?
>
> They have been for many years.
>
> --
> Grant Edwards
> grante@visi.com
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
next prev parent reply other threads:[~2003-10-23 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 18:30 ARM Larry McCourry
2003-10-23 18:34 ` ARM Grant Edwards
2003-10-23 18:50 ` Larry McCourry [this message]
2003-10-23 19:08 ` ARM Grant Edwards
2003-10-23 20:18 ` ARM Jim Blandy
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='000c01c39995$77fd1f40$6401a8c0@betsy' \
--to=lmccourry@charter.net \
--cc=gdb@sources.redhat.com \
--cc=grante@visi.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