Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Julian Brown <julian@codesourcery.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: [PATCH] Displaced stepping (non-stop debugging) support for  ARM Linux
Date: Fri, 24 Jul 2009 02:17:00 -0000	[thread overview]
Message-ID: <20090723221931.GA25885@caradoc.them.org> (raw)
In-Reply-To: <20090715192749.718691f1@rex.config>

On Wed, Jul 15, 2009 at 07:27:49PM +0100, Julian Brown wrote:
> One possibly dubious part though is the positioning of the
> insert_breakpoints() call in arm-linux-tdep.c:arm_linux_copy_svc():
> without that, the momentary breakpoint used to regain control after a
> sigreturn syscall never actually gets inserted into the debugged
> program, because the displaced-step copy function gets called after
> that normally happens. It should be safe AFAICT, but I may have
> overlooked something.

set_momentary_breakpoint calls update_global_location_list_nothrow.
That's supposed to insert breakpoints.  Here it is:

  if (breakpoints_always_inserted_mode () && should_insert
      && (have_live_inferiors ()
          || (gdbarch_has_global_breakpoints (target_gdbarch))))
    insert_breakpoint_locations ();

I'm guessing that you're using displaced stepping, but don't have
breakpoints always inserted (as they would be in typical use, since
non-stop requires it)?

I wish there were a more robust way to manage this, but I'm not sure
what it would be.  We could do it centrally after setting up displaced
stepping.  What you have seems OK to me.

In fact, both patches look OK to apply.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-07-23 22:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 22:14 Julian Brown
2009-01-21 18:07 ` Pedro Alves
2009-02-02 20:01 ` Daniel Jacobowitz
2009-05-16 18:19   ` Julian Brown
2009-06-09 17:37     ` Daniel Jacobowitz
2009-06-10 14:58       ` Pedro Alves
2009-06-10 15:05         ` Daniel Jacobowitz
2009-07-15 19:16           ` Julian Brown
2009-07-24  2:17             ` Daniel Jacobowitz [this message]
2009-07-31 11:43             ` Julian Brown
2009-09-24 19:35               ` Ulrich Weigand
2009-09-27 21:47                 ` [rfc] Fix PowerPC displaced stepping regression Ulrich Weigand
2009-09-28 16:57                   ` Pedro Alves
2009-09-28 17:12                     ` Ulrich Weigand
2009-09-28 17:31                       ` Pedro Alves
2009-09-28 17:39                         ` Ulrich Weigand
2009-09-28 17:27                     ` Ulrich Weigand
2009-09-28 17:39                       ` Pedro Alves
2009-09-28 17:45                         ` Ulrich Weigand
2009-09-28 19:07                           ` Pedro Alves
2009-09-28 19:41                   ` Pedro Alves
2009-09-29  0:59                     ` Ulrich Weigand
2009-09-29  1:36                       ` Joel Brobecker
2009-09-29 12:54                         ` Ulrich Weigand

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=20090723221931.GA25885@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=julian@codesourcery.com \
    --cc=pedro@codesourcery.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