From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/4] No longer handle negative 'step' in 'proceed'
Date: Wed, 11 Mar 2015 14:40:00 -0000 [thread overview]
Message-ID: <1426084798-1032-2-git-send-email-palves@redhat.com> (raw)
In-Reply-To: <1426084798-1032-1-git-send-email-palves@redhat.com>
Nothing ever passes a negative 'step' to proceed.
Gets rid of one of the few remaining stop_after_trap references.
gdb/ChangeLog
2015-03-11 Pedro Alves <palves@redhat.com>
* infrun.c (proceed): No longer handle negative step.
---
gdb/infrun.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/gdb/infrun.c b/gdb/infrun.c
index 0f8f531..ed4ba79 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -2588,10 +2588,8 @@ proceed (CORE_ADDR addr, enum gdb_signal siggnal, int step)
pc = regcache_read_pc (regcache);
tp = inferior_thread ();
- if (step > 0)
+ if (step)
step_start_function = find_pc_function (pc);
- if (step < 0)
- stop_after_trap = 1;
/* Fill in with reasonable starting values. */
init_thread_stepping_state (tp);
--
1.9.3
next prev parent reply other threads:[~2015-03-11 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 14:40 [PATCH 0/4] Make "set scheduler-locking step" depend on user intention, only Pedro Alves
2015-03-11 14:40 ` Pedro Alves [this message]
2015-03-11 14:40 ` [PATCH 3/4] " Pedro Alves
2015-03-18 20:06 ` Pedro Alves
2015-03-18 20:22 ` Eli Zaretskii
2015-10-22 7:21 ` Jan Kratochvil
2015-03-11 14:40 ` [PATCH 2/4] Make step_start_function be per thread Pedro Alves
2015-03-11 14:40 ` [PATCH 4/4] Remove 'step' parameters from 'proceed' and 'resume' Pedro Alves
2015-03-24 18:07 ` [PATCH 0/4] Make "set scheduler-locking step" depend on user intention, only Pedro Alves
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=1426084798-1032-2-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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