From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Pass inferior to terminal_save_inferior
Date: Tue, 23 Oct 2018 20:56:00 -0000 [thread overview]
Message-ID: <92a6ed25-426a-ef57-604a-1c9de3d83f2e@polymtl.ca> (raw)
In-Reply-To: <048ffbfd-e9b8-d223-f59d-d0b7dc139f04@redhat.com>
On 2018-10-23 7:11 a.m., Pedro Alves wrote:
> Oh, in that case it'd be clearer to not bundle it in the same series then.
Right, I happened to write it at the same time (when trying to figure out
how things worked) but it's not actually related.
>> Can't you access the inferior's target stack directly instead of changing the current inferior?
>
> I can for the call to the top target, but then the problem is the beneath()
> calls in all the target-delegates.c delegating implementations. E.g. here:
>
> void
> -target_ops::terminal_save_inferior ()
> +target_ops::terminal_save_inferior (inferior *arg0)
> {
> - this->beneath ()->terminal_save_inferior ();
> + this->beneath ()->terminal_save_inferior (arg0);
> ^^^^^^^^^
> }
>
> because beneath() looks at the target stack of the current
> inferior. It would need to look for the target beneath in
> the target stack of the arg0 inferior instead. Otherwise
> you start the top target call in inferior B, and then
> cross the the beneath target of inferior A (the current inferior).
> Whoops. At some point in the branch I made target_ops::beneath
> take an optional inferior pointer, but when I stumbled on this
> issue in target-delegates.c I ended up reverting it, as it
> wasn't easy to fix. I think that we could maybe teach
> make-target-delegates to automatically emit
>
> void
> target_ops::method (inferior *arg0)
> {
> this->beneath (arg0)->method (arg0);
> }
>
> and:
>
> void
> target_ops::method (thread_info *arg0)
> {
> this->beneath (arg0->inf)->method (arg0);
> }
>
> iff the method's first parameter is an inferior or thread_info
> pointer. But that was just an idea, I never toyed with it,
> because it would be a detour. So I gave up on the inferior
> parameter to target beneath, and thought I'd better focus instead
> of getting the multi-target basics in first, even if that means we
> need to swap current inferior/thread here and there, as usual.
Ok I understand. At some point I think it would be very nice if it
"just worked", but I totally understand the need to go by small
increment. In that case, I think I'll drop patches 1 and 2, since
they don't really provide any benefit at the moment, and just cause
complications going further.
Simon
prev parent reply other threads:[~2018-10-23 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 3:38 Simon Marchi
2018-10-16 3:38 ` [PATCH 2/3] Pass inferior to terminal_inferior Simon Marchi
2018-10-22 20:54 ` Pedro Alves
2018-10-23 9:14 ` Simon Marchi
2018-10-16 3:38 ` [PATCH 3/3] Avoid GDB SIGTTOU on catch exec + set follow-exec-mode new (PR 23368) Simon Marchi
[not found] ` <37bde004-853a-3ccc-3777-03cc43b36147@redhat.com>
2018-10-20 15:14 ` Simon Marchi
2018-10-20 15:38 ` Simon Marchi
2018-10-22 20:56 ` Pedro Alves
2018-10-23 9:49 ` Simon Marchi
2018-10-23 10:55 ` Pedro Alves
[not found] ` <mvmftwvr8ao.fsf@suse.de>
2018-10-24 14:08 ` Simon Marchi
2018-10-22 20:54 ` [PATCH 1/3] Pass inferior to terminal_save_inferior Pedro Alves
2018-10-23 9:01 ` Simon Marchi
2018-10-23 11:11 ` Pedro Alves
2018-10-23 20:56 ` 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=92a6ed25-426a-ef57-604a-1c9de3d83f2e@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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