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] Reapply: List inferiors/threads/pspaces in ascending order
Date: Tue, 12 Jan 2016 01:37:00 -0000	[thread overview]
Message-ID: <b05b120205e697db6291abb95a8cd2be054f99e9@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT b05b120205e697db6291abb95a8cd2be054f99e9 ***

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

Reapply: List inferiors/threads/pspaces in ascending order

[This reapplies a change that was accidentally reverted with c0ecb95f3d.]

Before:
  (gdb) info threads
    Id   Target Id         Frame
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92

After:
  (gdb) info threads
    Id   Target Id         Frame
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30

gdb/doc/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.texinfo (Inferiors and Programs): Adjust "maint info
	program-spaces" example to ascending order listing.
	(Threads): Adjust "info threads" example to ascending order
	listing.
	(Forks): Adjust "info inferiors" example to ascending order
	listing.

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* inferior.c (add_inferior_silent): Append the new inferior to the
	end of the list.
	* progspace.c (add_program_space): Append the new pspace to the
	end of the list.
	* thread.c (new_thread): Append the new thread to the end of the
	list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.base/foll-exec-mode.exp: Adjust to GDB listing inferiors and
	threads in ascending order.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.mi/mi-nonstop.exp: Likewise.
	* gdb.mi/mi-nsintrall.exp: Likewise.
	* gdb.multi/base.exp: Likewise.
	* gdb.multi/multi-arch.exp: Likewise.
	* gdb.python/py-inferior.exp: Likewise.
	* gdb.threads/break-while-running.exp: Likewise.
	* gdb.threads/execl.exp: Likewise.
	* gdb.threads/gcore-thread.exp: Likewise.
	* gdb.threads/info-threads-cur-sal.exp: Likewise.
	* gdb.threads/kill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/multiple-step-overs.exp: Likewise.
	* gdb.threads/next-bp-other-thread.exp: Likewise.
	* gdb.threads/step-bg-decr-pc-switch-thread.exp: Likewise.
	* gdb.threads/step-over-lands-on-breakpoint.exp: Likewise.
	* gdb.threads/step-over-trips-on-watchpoint.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.
	* lib/mi-support.exp (mi_reverse_list): Delete.
	(mi_check_thread_states): No longer reverse list.


             reply	other threads:[~2016-01-12  1:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  1:37 sergiodj+buildbot [this message]
2016-01-12  1:37 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12  1:38 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-01-12  1:38 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-12  1:45 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-01-12  1:47 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-01-12  1:49 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-01-12  1:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-01-12  1:56 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-01-12  2:06 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-01-12  2:06 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-01-12  2:07 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-01-12  2:09 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-01-12  2:16 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-01-12  2:19 ` Failures on Debian-i686, " sergiodj+buildbot
2016-01-12  2:22 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-12  2:39 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-01-12  2:41 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-01-12  2:52 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-12  2:57 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-01-12  2:57 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-01-12  3:33 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-01-12  7:07 ` Failures on Debian-x86_64-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=b05b120205e697db6291abb95a8cd2be054f99e9@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).