public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom de Vries <tdevries@suse.de>, Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches\\@sourceware.org" <gdb-patches@sourceware.org>,
	Kevin Buettner <kevinb@redhat.com>,
	Andreas Arnez <arnez@linux.ibm.com>,
	Luis Machado <luis.machado@linaro.org>, nd <nd@arm.com>,
	Andrew Burgess <andrew.burgess@embecosm.com>,
	palmer@dabbelt.com
Subject: Re: [PATCH][gdb/tdep] Use pid to choose x86_64 process 64/32-bitness
Date: Sat, 22 May 2021 21:27:52 -0400	[thread overview]
Message-ID: <172a4491-d783-c851-9f5f-5c0f6ea98713@polymtl.ca> (raw)
In-Reply-To: <bb2ce2a2-95d5-b972-eea9-64a5f0b760df@suse.de>


>> diff --git a/gdb/target.h b/gdb/target.h
>> index d867a58e2a8..51139042691 100644
>> --- a/gdb/target.h
>> +++ b/gdb/target.h
>> @@ -841,7 +841,10 @@ struct target_ops
>>      /* Describe the architecture-specific features of this target.  If
>>         OPS doesn't have a description, this should delegate to the
>>         "beneath" target.  Returns the description found, or NULL if no
>> -       description was available.  */
>> +       description was available.  This should return something that
>> +       describes a whole process, and if there are things that are
>> +       thread-specific, target_thread_architecture should be used for
>> +       that.  */

Haha, that sounds like the way I said it, which is a bit too informal
for a comment I think.  Here's what I suggest:

    /* Describe the architecture-specific features of the current
       inferior.

       Returns the description found, or nullptr if no description was
       available.

       If some target features differ between threads, the description
       returned by read_description (and the resulting gdbarch) won't
       accurately describe all threads.  In this case, the
       thread_architecture method can be used to obtain gdbarches that
       accurately describe each thread.  */

The patch LGTM with that.

Simon

      reply	other threads:[~2021-05-23  1:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07  8:44 Tom de Vries
2021-05-07 19:27 ` Simon Marchi
2021-05-07 20:06   ` Luis Machado
2021-05-19 16:32   ` Tom de Vries
2021-05-20 10:42     ` Alan Hayward
2021-05-20 16:07       ` Simon Marchi
2021-05-21 10:50         ` Alan Hayward
2021-05-22  8:32           ` Tom de Vries
2021-05-22  9:56             ` Tom de Vries
2021-05-23  1:27               ` Simon Marchi [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=172a4491-d783-c851-9f5f-5c0f6ea98713@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=Alan.Hayward@arm.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=arnez@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=luis.machado@linaro.org \
    --cc=nd@arm.com \
    --cc=palmer@dabbelt.com \
    --cc=tdevries@suse.de \
    /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).