From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gdb@sourceware.org
Cc: Dalibor Kovacevic <malonj@gmail.com>
Subject: Re: Fwd: Porting GDB to new architecture
Date: Thu, 11 Nov 2010 15:51:00 -0000 [thread overview]
Message-ID: <1289490700.3105.193.camel@thomas> (raw)
In-Reply-To: <AANLkTi=fZT=p=ALxATS6wn5q1h=9_S6sHoMzZM8GPs+F@mail.gmail.com>
On Thu, 2010-11-11 at 15:43 +0100, Dalibor Kovacevic wrote:
> I'm porting gdb 7.2 to a new architecture and I need a few tips to get
> me started. I have read all about porting gdb that google search found
> on that subject. The HOW TO from Jeremy Bennett helped me allot to
> understand what I need to do. But before the start of porting I was
> wondering could someone help me choose the starting template from
> already ported architectures. Mine is a combination of DSP
> and a microcontroller, binutils are already ported so i have BFD, it
> will be debugged via stub.
Hi Dalibor,
Glad you found the HOWTO useful. I need to update it for GDB 7.x. In
particular the frame handling has changed, so the functions use THIS
frame as the handle, rather than the NEXT frame. The function names have
changed accordingly.
I took my examples from the OpenRISC 1000, which is a MIPS like RISC
architecture. It's not part of the official GDB distribution (yet!), but
you can find the source code at
http://opencores.org/openrisc,gnu_toolchain
Because I used it in the HOWTO, the code is commented rather more
verbosely than other ports, so you may find it a useful example to look
at. There is a 7.2 version, which will help you with the new function
names.
HTH,
Jeremy
--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
prev parent reply other threads:[~2010-11-11 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=kw0fJaRDKrppfq0y=SrA2URGGnSp08whozgp0@mail.gmail.com>
2010-11-11 14:44 ` Dalibor Kovacevic
2010-11-11 15:51 ` Jeremy Bennett [this message]
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=1289490700.3105.193.camel@thomas \
--to=jeremy.bennett@embecosm.com \
--cc=gdb@sourceware.org \
--cc=malonj@gmail.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