From: Don Breazeal <donb@codesourcery.com>
To: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Target remote mode fork and exec events
Date: Fri, 20 Nov 2015 16:50:00 -0000 [thread overview]
Message-ID: <564F4F33.4030906@codesourcery.com> (raw)
In-Reply-To: <564F1A6A.3030301@redhat.com>
On 11/20/2015 5:04 AM, Pedro Alves wrote:
> Hi Don,
>
> Thanks for doing this. Starting to look at the series.
Thanks!
>
> On 11/06/2015 11:56 PM, Don Breazeal wrote:
>> This patch implements support for fork and exec events with target remote
>> mode Linux targets. For such targets with Linux kernels 2.5.46 and later,
>> this enables follow-fork-mode, detach-on-fork and fork and exec
>> catchpoints.
>
>> Note that follow-exec-mode is not supported, because target
>> remote mode does not support the 'run' command.
>
> Not sure I don't understand this part/comment.
I assume that we agree that the 'run' command is not supported in target
remote mode.
Maybe a better way to have stated this would be that follow-exec-mode is
of limited used in target remote mode, since the 'run' command is not
supported. The point being that the main reason a user would want to
set follow-exec-mode would be to get control over which inferior is run
when a 'run' command is executed.
I have to admit that it is incorrect to say that it is unsupported,
since setting follow-exec-mode *will* control whether a new inferior or
the same inferior is used for the execed program. But there isn't much
you can do differently without the 'run' command. Using
follow-exec-mode 'new' there *is* a record of what programs have been
run, which could be useful.
Is that a more accurate description, or am I misunderstanding something?
I'll get to work on the rest of this, hopefully sometime next week.
thanks
--Don
next prev parent reply other threads:[~2015-11-20 16:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 23:56 [PATCH 0/3] Target remote mode fork and exec support Don Breazeal
2015-11-06 23:57 ` [PATCH 3/3] Target remote mode fork and exec docs Don Breazeal
2015-11-07 8:18 ` Eli Zaretskii
2015-11-12 1:00 ` Don Breazeal
2015-11-12 1:00 ` Don Breazeal
2015-11-12 16:48 ` Eli Zaretskii
2015-11-13 1:13 ` Don Breazeal
2015-11-13 8:16 ` Eli Zaretskii
2015-11-06 23:57 ` [PATCH 1/3] Target remote mode fork and exec events Don Breazeal
2015-11-20 13:04 ` Pedro Alves
2015-11-20 16:50 ` Don Breazeal [this message]
2015-12-07 22:14 ` [PATCH v2 0/3] Target remote mode fork and exec support Don Breazeal
2015-12-07 22:14 ` [PATCH v2 1/3] Target remote mode fork and exec tests Don Breazeal
2015-12-08 12:58 ` Pedro Alves
2015-12-14 19:29 ` [pushed] " Don Breazeal
2015-12-07 22:14 ` [PATCH v2 2/3] Target remote mode fork and exec events Don Breazeal
2015-12-08 12:55 ` Pedro Alves
2015-12-14 19:29 ` Don Breazeal
2015-12-15 10:52 ` Pedro Alves
2015-12-07 22:15 ` [PATCH v2 3/3] Target remote mode fork and exec docs Don Breazeal
2015-12-08 13:07 ` Pedro Alves
2015-12-14 19:30 ` [pushed] " Don Breazeal
2015-12-08 13:11 ` [PATCH v2 0/3] Target remote mode fork and exec support Pedro Alves
2015-11-06 23:57 ` [PATCH 2/3] Target remote mode fork and exec tests Don Breazeal
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=564F4F33.4030906@codesourcery.com \
--to=donb@codesourcery.com \
--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