From: Jonathan Larmour <jifl@eCosCentric.com>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] PPC - Stepping off breakpoints in non-stop mode
Date: Tue, 08 Jul 2008 01:39:00 -0000 [thread overview]
Message-ID: <4872C52C.1020701@eCosCentric.com> (raw)
Luis Machado wrote:
> [...]
> Checked in the following.
> [...]
> 2008-06-30 Luis Machado <luisgpm@br.ibm.com>
>
> * rs6000-tdep.c (ppc_displaced_step_fixup): New function.
> (deal_with_atomic_sequence): Update BC masks.
> (rs6000_gdbarch_init): Init displaced stepping infra-structure.
> Define BRANCH_MASK, B_INSN, BC_INSN, BXL_INSN, BP_MASK and BP_INSN.
Unfortunately this fails to build due to this warning (in combination with
-Werror):
.../rs6000-tdep.c: In function âppc_displaced_step_fixupâ:
.../rs6000-tdep.c:885: warning: passing argument 3 of
âregcache_cooked_read_unsignedâ from incompatible pointer type
make[2]: *** [rs6000-tdep.o] Error 1
This is because in the following line, current_pc is CORE_ADDR, but
regcache_cooked_read_unsigned's last arg is meant to be a ULONGEST *.
+ regcache_cooked_read_unsigned (regs, gdbarch_pc_regnum (gdbarch),
+ ¤t_pc);
I was thinking of just casting it, but in fact would it be better to be
calling regcache_read_pc() here as well as regcache_write_pc() in the rest
of the patch when operating on the pc? From earlier in this thread, there
was a little discussion about address sizes, so I thought I'd best ask
before submitting a patch, as there could be portability implications and
it might have been done this way for a reason.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
next reply other threads:[~2008-07-08 1:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 1:39 Jonathan Larmour [this message]
2008-07-08 3:53 ` Luis Machado
2008-07-08 14:59 ` Jonathan Larmour
2008-07-08 15:13 ` Luis Machado
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 20:26 Luis Machado
2008-05-19 15:20 ` Pedro Alves
2008-05-19 15:21 ` Luis Machado
2008-05-29 15:41 ` Luis Machado
2008-06-05 20:03 ` Daniel Jacobowitz
2008-06-06 16:00 ` Luis Machado
2008-06-24 14:59 ` Luis Machado
2008-06-24 18:08 ` Pedro Alves
2008-06-24 18:19 ` Luis Machado
2008-06-25 12:54 ` Joel Brobecker
2008-06-25 13:35 ` Luis Machado
2008-06-25 13:51 ` Joel Brobecker
2008-06-25 15:48 ` Luis Machado
2008-06-25 18:49 ` Joel Brobecker
2008-06-30 17:04 ` Luis Machado
2008-05-19 15:20 ` Luis Machado
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=4872C52C.1020701@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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