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] Add Python InferiorThread.global_num attribute
Date: Wed, 13 Jan 2016 11:40:00 -0000	[thread overview]
Message-ID: <22a0232400ea09c57ab70d97cffc1f25e6320da7@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 22a0232400ea09c57ab70d97cffc1f25e6320da7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 22a0232400ea09c57ab70d97cffc1f25e6320da7

Add Python InferiorThread.global_num attribute

This commit adds a new Python InferiorThread.global_num attribute.
This can be used to pass the correct thread ID to Breakpoint.thread,
which takes a global thread ID, not a per-inferior thread number.

gdb/ChangeLog:
2016-01-13  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention InferiorThread.global_num.
	* python/py-infthread.c (thpy_get_global_num): New function.
	(thread_object_getset): Register "global_num".

gdb/testsuite/ChangeLog:
2016-01-13  Pedro Alves  <palves@redhat.com>

	* gdb.multi/tids.exp: Test InferiorThread.global_num and
	Breakpoint.thread.
	* gdb.python/py-infthread.exp: Test InferiorThread.global_num.

gdb/doc/ChangeLog:
2016-01-13  Pedro Alves  <palves@redhat.com>

	* python.texi (Breakpoints In Python) <Breakpoint.thread>: Add
	anchor.
	(Threads In Python): Document new InferiorThread.global_num
	attribute.


             reply	other threads:[~2016-01-13 11:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 11:40 sergiodj+buildbot [this message]
2016-01-13 11:40 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2016-01-13 11:40 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-01-13 11:41 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-13 12:34 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-01-13 13:44 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-01-13 13:47 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-13 13:50 ` Failures on Fedora-x86_64-cxx-build-m64, " sergiodj+buildbot
2016-01-13 13:52 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-01-13 13:55 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-01-13 14:00 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-01-13 14:41 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-01-13 16:19 ` Failures on Debian-i686, " sergiodj+buildbot
2016-01-13 16:39 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-01-13 17:02 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-01-13 18:20 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-01-13 18:31 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-13 18:40 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-01-13 18:50 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-01-13 19:06 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-01-13 19:07 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-01-13 19:16 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " 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=22a0232400ea09c57ab70d97cffc1f25e6320da7@gdb-build \
    --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).