From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: uweigand@de.ibm.com
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [patch] "single step" atomic instruction sequences as a whole.
Date: Sat, 14 Apr 2007 15:20:00 -0000 [thread overview]
Message-ID: <200704140815.l3E8FAWR004193@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200704122043.l3CKhnTB019216@d12av02.megacenter.de.ibm.com> (uweigand@de.ibm.com)
> Date: Thu, 12 Apr 2007 22:43:49 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
>
> Mark Kettenis wrote:
>
> > I suspect the write_pc call is there to make stepping delay-slot
> > instructions work.
>
> Maybe I'm confused, but I thought alpha didn't have delay slots?
> There is a special gdbarch routine single_step_through_delay for
> targets that have those ...
Duh, you're right. I must have been hacking tto much on sparc64 and
mips64 lately.
> > > I don't have a way to test on alpha-linux unfortunately. Do you?
> >
> > I can test OpenBSD/alpha later this week if necessary.
>
> Thanks for the offer! (I just noticed that Linux/alpha doesn't use
> software single-step anyway, but OpenBSD/alpha does.)
Indeed.
> Would you mind testing this small patch that simply removes the
> write_pc call?
It actually gets rid of a couple of FAILs. So please go ahead and
commit this.
> * alpha-tdep.c (alpha_software_single_step): Do not call write_pc
> when removing single-step breakpoints.
>
> Index: gdb/alpha-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/alpha-tdep.c,v
> retrieving revision 1.163
> diff -u -p -r1.163 alpha-tdep.c
> --- gdb/alpha-tdep.c 12 Apr 2007 14:52:19 -0000 1.163
> +++ gdb/alpha-tdep.c 12 Apr 2007 20:39:08 -0000
> @@ -1521,7 +1521,7 @@ alpha_next_pc (CORE_ADDR pc)
> int
> alpha_software_single_step (enum target_signal sig, int insert_breakpoints_p)
> {
> - static CORE_ADDR next_pc;
> + CORE_ADDR next_pc;
> CORE_ADDR pc;
>
> if (insert_breakpoints_p)
> @@ -1534,7 +1534,6 @@ alpha_software_single_step (enum target_
> else
> {
> remove_single_step_breakpoints ();
> - write_pc (next_pc);
> }
> return 1;
> }
next prev parent reply other threads:[~2007-04-14 8:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 22:24 Luis Machado
2007-04-10 20:40 ` Daniel Jacobowitz
2007-04-12 12:09 ` Luis Machado
2007-04-12 12:15 ` Daniel Jacobowitz
2007-04-12 12:54 ` Luis Machado
2007-04-12 12:58 ` Daniel Jacobowitz
2007-04-12 13:30 ` Luis Machado
2007-04-12 13:35 ` Daniel Jacobowitz
2007-04-12 14:58 ` Ulrich Weigand
2007-04-12 15:33 ` Daniel Jacobowitz
2007-04-12 17:16 ` Ulrich Weigand
2007-04-12 18:25 ` Daniel Jacobowitz
2007-04-12 20:09 ` Ulrich Weigand
2007-04-12 20:16 ` Mark Kettenis
2007-04-12 20:43 ` Ulrich Weigand
2007-04-14 15:20 ` Mark Kettenis [this message]
2007-04-14 18:13 ` Ulrich Weigand
2007-04-12 20:49 ` Daniel Jacobowitz
2007-04-12 20:48 ` Daniel Jacobowitz
2007-04-14 18:50 ` [commit] Update software_single_step arguments Ulrich Weigand
2007-04-12 14:32 ` [patch] "single step" atomic instruction sequences as a whole Ulrich Weigand
2007-04-12 14:47 ` Luis Machado
2007-04-12 15:00 ` Ulrich Weigand
-- strict thread matches above, loose matches on Subject: below --
2007-02-17 2:24 Luis Machado
2007-02-27 13:00 ` Emi SUZUKI
2007-02-27 13:17 ` Daniel Jacobowitz
2007-02-28 8:08 ` Emi SUZUKI
2007-02-28 11:46 ` Daniel Jacobowitz
2007-02-28 16:09 ` Luis Machado
2007-03-02 12:47 ` Emi SUZUKI
2007-03-06 11:00 ` Andreas Schwab
2007-03-06 12:24 ` Daniel Jacobowitz
2007-03-08 8:50 ` Emi SUZUKI
2007-03-08 16:15 ` Ulrich Weigand
2007-03-13 6:12 ` SUZUKI Emi
2007-02-06 11:02 Luis Machado
2007-02-06 12:11 ` Emi SUZUKI
2007-02-07 13:10 ` Luis Machado
2007-02-08 13:00 ` Emi SUZUKI
2006-09-18 11:59 emin ak
2006-11-09 13:07 ` [patch] " emin ak
2006-06-22 20:56 PAUL GILLIAM
2006-06-22 21:53 ` PAUL GILLIAM
2006-06-22 22:20 ` PAUL GILLIAM
2006-11-10 21:18 ` Daniel Jacobowitz
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=200704140815.l3E8FAWR004193@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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