Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: palves@redhat.com, brobecker@adacore.com
Cc: gdb-patches@sourceware.org,
	Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [PATCH V2 1/2] Bound violation handling preparation.
Date: Fri, 18 Dec 2015 13:44:00 -0000	[thread overview]
Message-ID: <1450446270-27887-1-git-send-email-walfred.tedeschi@intel.com> (raw)

In the place notifier was the inferior is still not stopped.
Moved the observer to where the inferior is already signaled as stopped
and evaluation can be done.

2015-12-15  Walfred Tedeschi  <walfred.tedeschi@intel.com>

	* infrun.c (normal_stop): Change observers placement within
	the function.

---
 gdb/infrun.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gdb/infrun.c b/gdb/infrun.c
index f9bb411..2ed807c 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -8174,9 +8174,6 @@ normal_stop (void)
      instead of after.  */
   update_thread_list ();
 
-  if (last.kind == TARGET_WAITKIND_STOPPED && stopped_by_random_signal)
-    observer_notify_signal_received (inferior_thread ()->suspend.stop_signal);
-
   /* As with the notification of thread events, we want to delay
      notifying the user that we've switched thread context until
      the inferior actually stops.
@@ -8282,6 +8279,9 @@ normal_stop (void)
       do_cleanups (old_chain);
     }
 
+  if (last.kind == TARGET_WAITKIND_STOPPED && stopped_by_random_signal)
+    observer_notify_signal_received (inferior_thread ()->suspend.stop_signal);
+
   /* Notify observers about the stop.  This is where the interpreters
      print the stop event.  */
   if (!ptid_equal (inferior_ptid, null_ptid))
-- 
2.1.4


             reply	other threads:[~2015-12-18 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 13:44 Walfred Tedeschi [this message]
2015-12-18 13:44 ` [PATCH V2 2/2] Bound violation handling Walfred Tedeschi
  -- strict thread matches above, loose matches on Subject: below --
2015-12-17 17:06 [PATCH V2 1/2] Bound violation handling preparation Walfred Tedeschi

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=1450446270-27887-1-git-send-email-walfred.tedeschi@intel.com \
    --to=walfred.tedeschi@intel.com \
    --cc=brobecker@adacore.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