public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Make step_start_function be per thread
Date: Wed, 25 Mar 2015 00:47:00 -0000 [thread overview]
Message-ID: <885eeb5b8ea021cc79ffebe8ec40122229c572f0@kwanyin> (raw)
*** TEST RESULTS FOR COMMIT 885eeb5b8ea021cc79ffebe8ec40122229c572f0 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 885eeb5b8ea021cc79ffebe8ec40122229c572f0
Make step_start_function be per thread
I noticed that step_start_function is still a global, while it
obviously should be a per-thread field.
gdb/ChangeLog:
2015-03-24 Pedro Alves <palves@redhat.com>
* infrun.c (step_start_function): Delete and ...
* gdbthread.h (struct thread_control_state) <step_start_function>:
... now a field here.
* infrun.c (clear_proceed_status_thread): Clear the thread's
step_start_function.
(proceed, process_event_stop_test, print_stop_event): Adjust.
next reply other threads:[~2015-03-24 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 0:47 sergiodj+buildbot [this message]
2015-03-25 0:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2015-03-25 20:34 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-03-25 20:55 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-03-25 21:42 ` Failures on Debian-i686, " sergiodj+buildbot
2015-03-26 20:41 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-03-26 21:12 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-03-27 1:32 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-03-28 7:48 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
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=885eeb5b8ea021cc79ffebe8ec40122229c572f0@kwanyin \
--to=sergiodj+buildbot@redhat.com \
--cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).