Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org,
	Thomas Schwinge <thomas@codesourcery.com>,
	thomas@schwinge.name, bug-hurd@gnu.org
Subject: Re: [PATCHv2 6/7] hurd: add gnu_target pointer to fix thread API calls
Date: Sat, 30 May 2020 19:22:11 +0200	[thread overview]
Message-ID: <20200530172211.dt6xh33dhrdpa76r@function> (raw)
In-Reply-To: <4f5f1015-6b4f-1808-f6a4-bfedb0506f08@simark.ca>

Simon Marchi, le sam. 30 mai 2020 12:08:53 -0400, a ecrit:
> On 2020-05-30 11:53 a.m., Samuel Thibault wrote:
> > Simon Marchi, le sam. 30 mai 2020 10:57:42 -0400, a ecrit:
> >>> @@ -1106,12 +1109,12 @@ inf_validate_procs (struct inf *inf)
> >>>  	    if (inferior_ptid == ptid_t (inf->pid))
> >>>  	      /* This is the first time we're hearing about thread
> >>>  		 ids, after a fork-child.  */
> >>> -	      thread_change_ptid (inferior_ptid, ptid);
> >>> +	      thread_change_ptid (gnu_target, inferior_ptid, ptid);
> >>
> >>
> >> I think it would have been more straightforward and clean to use `inf->process_target ()`
> >> (assuming it's the correct thing to do), given that you have access to the appropriate
> >> inferior everywhere you made changes.
> > 
> > I didn't see a way to access the inferior here (inf is a
> > gnu-nat.c-specific structure with no link to struct inferior)
> 
> Ah I see.  Well, I didn't check all code paths, but for example, for the one that goes:
> 
> - gnu_nat_target::attach
> - inf_attach
> - inf_startup
> - inf_set_pid
> 
> A solution would be to make all these inf_* functions to be private methods of the
> gnu_nat_target class.

Ok, I see. thread_change_ptid is however also called from
inf_validate_procs, called from inf_update_procs, called from
i386_gnu_dr_set_control, referenced from the x86 backend
x86_dr_low.set_control = i386_gnu_dr_set_control;

For simplicity I'll keep gnu_target for now, but also work on cleaning
these should-be-static/private functions.

Samuel


  reply	other threads:[~2020-05-30 17:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 22:00 [PATCHv2 1/7] hurd: fix gnu_debug_flag type Samuel Thibault
2020-05-29 22:01 ` [PATCHv2 2/7] hurd: add missing awk script dependency Samuel Thibault
2020-05-30 14:42   ` Simon Marchi
2020-05-29 22:01 ` [PATCHv2 3/7] hurd: make function cast stronger Samuel Thibault
2020-05-30 14:47   ` Simon Marchi
2020-05-30 15:32     ` Samuel Thibault
2020-05-30 16:02       ` Simon Marchi
2020-05-29 22:02 ` [PATCHv2 4/7] hurd: add missing include Samuel Thibault
2020-05-30 14:48   ` Simon Marchi
2020-05-29 22:03 ` [PATCHv2 5/7] hurd: remove unused variables Samuel Thibault
2020-05-30 14:49   ` Simon Marchi
2020-05-29 22:03 ` [PATCHv2 6/7] hurd: add gnu_target pointer to fix thread API calls Samuel Thibault
2020-05-30 14:57   ` Simon Marchi
2020-05-30 15:53     ` Samuel Thibault
2020-05-30 16:08       ` Simon Marchi
2020-05-30 17:22         ` Samuel Thibault [this message]
2020-05-29 22:04 ` [PATCHv2 7/7] hurd: fix pushing target on inferior creation Samuel Thibault
2020-05-30 15:01   ` Simon Marchi
2020-05-30 14:39 ` [PATCHv2 1/7] hurd: fix gnu_debug_flag type Simon Marchi
2020-05-30 16:00   ` Samuel Thibault
2020-05-30 16:12     ` Simon Marchi
2020-05-30 16:53       ` Samuel Thibault
2020-05-30 17:38         ` Simon Marchi
2020-05-30 19:07 ` Samuel Thibault

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=20200530172211.dt6xh33dhrdpa76r@function \
    --to=samuel.thibault@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=thomas@codesourcery.com \
    --cc=thomas@schwinge.name \
    /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