From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 02/11] gdb: introduce intrusive_list, make thread_info use it
Date: Tue, 6 Jul 2021 17:38:52 -0400 [thread overview]
Message-ID: <8826cbc4-51a3-3ae4-150f-a119b660a02f@polymtl.ca> (raw)
In-Reply-To: <614bf906-7bfd-9864-5122-f5fc8dea8d05@palves.net>
On 2021-07-06 5:04 p.m., Pedro Alves wrote:
> On 2021-07-06 9:45 p.m., Simon Marchi wrote:
>> I tried this, it does work:
>>
>> $1 = intrusive list of struct thread_info = {
>> [0] = 0x61700003b180,
>> [1] = 0x61700003b500,
>> [2] = 0x61700003b880,
>> [3] = 0x61700003bc00
>> }
>>
>> However, I see this as going around / abusing our pretty-printing API.
>> If one doesn't want to see the indices, it becomes impossible (AFAIK).
>> If you want array-indexes, why not just set array-indexes on?
>
> I think you misunderstood me earlier -- I meant that I would probably switch on
> "set array-indexes on" all the time, as I'd find it difficult to use the
> pointer-only array without it, not that the printer would not respect
> the setting.
Ah, yes sorry. I understood it as if it was a bad thing that array
indices were not printed by default, and that it should be fixed in the
printer. So, nothing to see here :).
Simon
next prev parent reply other threads:[~2021-07-06 21:39 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 16:56 [PATCH 00/11] Various thread lists optimizations Simon Marchi
2021-06-22 16:56 ` [PATCH 01/11] gdb: introduce iterator_range, remove next_adapter Simon Marchi
2021-07-05 15:41 ` Pedro Alves
2021-07-06 19:16 ` Simon Marchi
2021-06-22 16:56 ` [PATCH 02/11] gdb: introduce intrusive_list, make thread_info use it Simon Marchi
2021-06-22 23:13 ` Lancelot SIX
2021-06-23 0:48 ` Simon Marchi
2021-07-05 15:44 ` Pedro Alves
2021-07-06 19:38 ` Simon Marchi
2021-07-06 20:45 ` Simon Marchi
2021-07-06 21:04 ` Pedro Alves
2021-07-06 21:38 ` Simon Marchi [this message]
2021-07-06 21:02 ` Pedro Alves
2021-07-06 21:45 ` Simon Marchi
2021-07-07 11:46 ` Pedro Alves
2021-07-07 13:52 ` Simon Marchi
2021-06-22 16:56 ` [PATCH 03/11] gdb: make inferior_list use intrusive_list Simon Marchi
2021-07-05 15:44 ` Pedro Alves
2021-07-14 6:34 ` Tom de Vries
2021-07-14 16:11 ` Simon Marchi
2021-07-14 20:15 ` [PATCH] gdb: make all_inferiors_safe actually work Simon Marchi
2021-07-15 10:15 ` Tom de Vries
2021-07-17 12:54 ` Simon Marchi
2021-06-22 16:56 ` [PATCH 04/11] gdb: use intrusive list for step-over chain Simon Marchi
2021-07-05 15:45 ` Pedro Alves
2021-07-06 20:59 ` Simon Marchi
2021-06-22 16:56 ` [PATCH 05/11] gdb: add setter / getter for thread_info resumed state Simon Marchi
2021-07-05 15:45 ` Pedro Alves
2021-06-22 16:56 ` [PATCH 06/11] gdb: make thread_info::suspend private, add getters / setters Simon Marchi
2021-07-05 15:45 ` Pedro Alves
2021-06-22 16:57 ` [PATCH 07/11] gdb: maintain per-process-target list of resumed threads with pending wait status Simon Marchi
2021-07-05 15:51 ` Pedro Alves
2021-07-06 21:25 ` Simon Marchi
2021-07-07 12:01 ` Pedro Alves
2021-07-12 22:28 ` Simon Marchi
2021-07-12 22:34 ` Simon Marchi
2021-07-13 12:21 ` Pedro Alves
2021-06-22 16:57 ` [PATCH 08/11] gdb: optimize check for resumed threads with pending wait status in maybe_set_commit_resumed_all_targets Simon Marchi
2021-07-05 15:51 ` Pedro Alves
2021-06-22 16:57 ` [PATCH 09/11] gdb: optimize selection of resumed thread with pending event Simon Marchi
2021-07-05 15:51 ` Pedro Alves
2021-06-22 16:57 ` [PATCH 10/11] gdb: maintain ptid -> thread map, optimize find_thread_ptid Simon Marchi
2021-07-05 15:52 ` Pedro Alves
2021-07-06 21:31 ` Simon Marchi
2021-07-07 12:13 ` Pedro Alves
2021-06-22 16:57 ` [PATCH 11/11] gdb: optimize all_matching_threads_iterator Simon Marchi
2021-07-05 15:52 ` Pedro Alves
2021-07-14 9:40 ` Tom de Vries
2021-07-13 0:47 ` [PATCH 00/11] Various thread lists optimizations Simon Marchi
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=8826cbc4-51a3-3ae4-150f-a119b660a02f@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@efficios.com \
/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).