From: Pedro Alves <palves@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/6] PR 17539 - inferiors/threads etc. print in reverse order
Date: Tue, 24 Nov 2015 18:44:00 -0000 [thread overview]
Message-ID: <5654B021.3090801@redhat.com> (raw)
In-Reply-To: <1445507944-9197-1-git-send-email-palves@redhat.com>
On 10/22/2015 10:58 AM, Pedro Alves wrote:
> PR 17539 points out that "info inferiors" lists inferiors in
> decreasing order. I audited the "info" sub commands, and GDB is
> inconsistent on this issue in several places. Some commands list in
> ascending order, while others in descending order.
>
...
> This patch series switches all "descending order" commands I found to
> ascending order, and adjusts manual and testsuite accordingly.
>
> Pedro Alves (6):
> Make gdb.python/py-inferior.exp test names unique
> Linux: dump the signalled thread first
> List inferiors/threads/pspaces in ascending order
> List checkpoints in ascending order
> List displays in ascending order
> NEWS: "info" commands now list in ascending order
This is now pushed.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-11-24 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 10:56 Pedro Alves
2015-10-22 10:57 ` [PATCH 4/6] List checkpoints in ascending order Pedro Alves
2015-10-22 10:58 ` [PATCH 2/6] Linux: dump the signalled thread first Pedro Alves
2015-10-22 11:07 ` [PATCH 3/6] List inferiors/threads/pspaces in ascending order Pedro Alves
2015-10-22 16:03 ` Eli Zaretskii
2016-01-08 20:39 ` Regression for gdb.threads/fork-plus-threads.exp [Re: [PATCH 3/6] List inferiors/threads/pspaces in ascending order] Jan Kratochvil
2016-01-11 14:40 ` Pedro Alves
2016-01-12 11:22 ` Pedro Alves
2016-01-13 0:37 ` Pedro Alves
2015-10-22 11:23 ` [PATCH 1/6] Make gdb.python/py-inferior.exp test names unique Pedro Alves
2015-10-22 11:50 ` [PATCH 6/6] NEWS: "info" commands now list in ascending order Pedro Alves
2015-10-22 16:00 ` Eli Zaretskii
2015-10-22 16:06 ` Pedro Alves
2015-10-22 16:16 ` Eli Zaretskii
2015-10-22 12:36 ` [PATCH 5/6] List displays " Pedro Alves
2015-11-24 18:44 ` Pedro Alves [this message]
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=5654B021.3090801@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