From: Yao Qi <yao@codesourcery.com>
To: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] New GDB Port CR16
Date: Thu, 30 Aug 2012 05:14:00 -0000 [thread overview]
Message-ID: <503EF699.1060700@codesourcery.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB65845B28633@KCHJEXMB03.kpit.com>
On 08/30/2012 12:49 PM, Kaushik Phatak wrote:
> I have another cr16-tdep.c file (might call it cr16-linux-tdep.c) that would
> work with the kernel port. They have slightly different register set and use
> different breakpoint instruction. I am still not sure how to go about that part.
We've handled different breakpoint instructions in other ports, and you
can follow the similar way for your port.
You need a 'struct gdbarch_tdep' defined in ${arch}-tdep.h, with a
field 'breakpoint', for example, which points to the exact breakpoint
instruction you'll use.
Set field 'breakpoint' in
${arch}-linux-tdep.c:${arch}_uclinux_init_abi according to some ELF
header or attributes.
Return correct breakpoint instruction in ${arch}_breakpoint_from_pc.
Set ${arch} to 'tic6x' above, you'll see the example in details.
With respect to different register sets, you may have to use 'target
description' feature in GDB.
--
Yao
prev parent reply other threads:[~2012-08-30 5:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 6:37 Kaushik Phatak
2012-08-27 16:21 ` Yao Qi
2012-08-28 14:47 ` Kaushik Phatak
2012-08-29 22:14 ` Mike Frysinger
2012-08-30 5:23 ` Kaushik Phatak
2012-08-30 6:10 ` Mike Frysinger
2012-09-03 9:31 ` Pedro Alves
2012-09-04 3:52 ` Mike Frysinger
2012-09-04 6:50 ` Kaushik Phatak
2012-09-07 17:47 ` Pedro Alves
2012-09-11 13:16 ` Kaushik Phatak
2012-09-11 19:02 ` Mike Frysinger
2012-09-24 12:55 ` Kaushik Phatak
2012-09-11 19:00 ` Mike Frysinger
2012-08-27 21:10 ` Mike Frysinger
2012-08-28 16:24 ` Pedro Alves
2012-08-30 4:49 ` Kaushik Phatak
2012-08-30 5:14 ` Yao Qi [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=503EF699.1060700@codesourcery.com \
--to=yao@codesourcery.com \
--cc=Kaushik.Phatak@kpitcummins.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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