From: Don Breazeal <donb@codesourcery.com>
To: <gdb-patches@sourceware.org>, <palves@redhat.com>
Subject: [PATCH v3 0/4] Extended-remote exec events
Date: Wed, 09 Sep 2015 23:05:00 -0000 [thread overview]
Message-ID: <1441839937-22251-1-git-send-email-donb@codesourcery.com> (raw)
In-Reply-To: <1438298360-29594-1-git-send-email-donb@codesourcery.com>
Hi Pedro,
Thanks for the previous review(s). This is an update to version 2 of the
extended-remote exec event patchset. The most significant differences from
the previous version include:
1) Gdbserver always creates a new inferior for an execing process.
2) GDB's 'remote exec-file' is now per-inferior instead off a static
string.
3) There is a new GDB target hook 'target_follow_exec'.
4) Elimination of patch #4, which eliminated spurious warnings
when setting up the solib event hook after an exec. The
patch was no longer needed after change #1 above.
5) Test and documentation updates per review comments.
Original description is unchanged below, except for eliminating
patch #4.
Thanks
--Don
--------------
This patch series implements exec events for extended-remote Linux targets.
It provides exec event notification, follow-exec functionality, and exec
catchpoints. Several tests related to exec event features have been
modified to work with the native-extended-gdbserver target.
It is part of the larger effort to implement "remote follow fork". This
work has been divided into three parts:
1) Extended-remote fork events, providing follow-fork-mode,
detach-on-fork, and fork catchpoints. This was pushed earlier this
year: https://sourceware.org/ml/gdb-patches/2015-05/msg00278.html
2) Extended-remote exec events, this patchset.
3) Fork and exec events for native-gdbserver target.
This patchset derives from part of a patch series submitted last October:
https://sourceware.org/ml/gdb-patches/2014-10/msg00868.html
The primary difference between this patchset and that one is that this
one does not use ptrace exit events (PTRACE_O_TRACEEXIT) for notification
of thread exit. In addition, a number of changes were made to conform to
to the final version of the extended-remote fork event patchset (#1 above).
Tested on x86_64 GNU/Linux with native, native-gdbserver, and
native-extended-gdbserver targets.
The contents of this patchset are as follows:
Patch 1/4: Extended-remote exec event support.
Patch 2/4: Extended-remote exec catchpoints.
Patch 3/4: Extended-remote exec-related test updates.
Patch 4/4: Extended-remote exec event documentation.
next prev parent reply other threads:[~2015-09-09 23:05 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 21:49 [PATCH 0/5] Extended-remote follow exec Don Breazeal
2015-07-15 21:50 ` [PATCH 3/5] Extended-remote support for exec event tests Don Breazeal
2015-07-15 21:50 ` [PATCH 2/5] Extended-remote exec catchpoints Don Breazeal
2015-08-13 15:00 ` Pedro Alves
2015-07-15 21:50 ` [PATCH 1/5] Extended-remote exec events Don Breazeal
2015-07-16 14:01 ` Yao Qi
2015-07-16 15:52 ` Don Breazeal
2015-07-16 16:35 ` Yao Qi
2015-07-16 17:06 ` Don Breazeal
2015-07-17 11:55 ` Yao Qi
2015-07-15 21:51 ` [PATCH 5/5] Extended-remote exec event docs Don Breazeal
2015-07-16 2:39 ` Eli Zaretskii
2015-07-15 21:51 ` [PATCH 4/5] Eliminate spurious warnings from remote exec Don Breazeal
2015-07-30 23:19 ` [PATCH v2 0/5] Extended-remote exec events Don Breazeal
2015-07-30 23:19 ` [PATCH v2 2/5] Extended-remote exec catchpoints Don Breazeal
2015-07-30 23:19 ` [PATCH v2 1/5] Extended-remote follow exec Don Breazeal
2015-08-13 14:50 ` Pedro Alves
2015-07-30 23:20 ` [PATCH v2 4/5] Eliminate spurious warnings from remote exec Don Breazeal
2015-08-13 15:38 ` Pedro Alves
2015-07-30 23:20 ` [PATCH v2 5/5] Extended-remote exec event docs Don Breazeal
2015-07-31 6:36 ` Eli Zaretskii
2015-07-31 17:06 ` Don Breazeal
2015-08-13 15:43 ` Pedro Alves
2015-07-30 23:20 ` [PATCH v2 3/5] Extended-remote support for exec event tests Don Breazeal
2015-08-13 15:22 ` Pedro Alves
2015-09-09 23:05 ` Don Breazeal [this message]
2015-09-09 23:06 ` [PATCH v3 3/4] " Don Breazeal
2015-09-10 13:26 ` Pedro Alves
2015-09-09 23:06 ` [PATCH v3 4/4] Extended-remote exec event docs Don Breazeal
2015-09-10 15:23 ` Eli Zaretskii
2015-09-09 23:06 ` [PATCH v3 2/4] Extended-remote exec catchpoints Don Breazeal
2015-09-09 23:06 ` [PATCH v3 1/4] Extended-remote follow exec Don Breazeal
2015-09-10 12:43 ` Pedro Alves
2015-09-10 22:56 ` Don Breazeal
2015-09-10 23:00 ` Don Breazeal
2015-09-11 8:34 ` Pedro Alves
2015-09-11 18:38 ` [pushed][PATCH " Don Breazeal
2015-09-11 18:38 ` [pushed][PATCH v3 3/4] Extended-remote exec test Don Breazeal
2015-09-15 15:45 ` Pedro Alves
2015-09-15 15:53 ` Don Breazeal
2015-09-15 15:58 ` Pedro Alves
2015-09-15 16:00 ` Breazeal, Don
2015-09-15 16:28 ` Pedro Alves
2015-09-11 18:38 ` [pushed][PATCH v3 2/4] Extended-remote exec catchpoints Don Breazeal
2015-09-11 18:39 ` [pushed][PATCH v3 4/4] Extended-remote exec event docs Don Breazeal
2015-09-15 8:56 ` [pushed][PATCH v3 1/4] Extended-remote follow exec Yao Qi
2015-09-15 16:12 ` Don Breazeal
2015-09-15 16:31 ` Yao Qi
2015-09-30 16:20 ` Pedro Alves
2015-09-30 16:22 ` Breazeal, Don
2016-12-08 11:54 ` Thomas Schwinge
2017-02-17 16:45 ` Pedro Alves
2019-02-14 16:42 ` Thomas Schwinge
2019-02-14 17:26 ` Tom Tromey
2019-02-14 23:11 ` Tom Tromey
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=1441839937-22251-1-git-send-email-donb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).