From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gbenson@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Use gdb_sysroot for main executable on attach
Date: Thu, 05 Mar 2015 12:49:00 -0000 [thread overview]
Message-ID: <201503051248.t25CmnZH014990@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1425555461-22093-1-git-send-email-gbenson@redhat.com> (message from Gary Benson on Thu, 5 Mar 2015 11:37:39 +0000)
> From: Gary Benson <gbenson@redhat.com>
> Date: Thu, 5 Mar 2015 11:37:39 +0000
>
> Hi all,
>
> This series modifies GDB to prefix the main executable's path with
> gdb_sysroot under certain circumstances, namely:
>
> * The path supplied by target_pid_to_exec_file is absolute, and
> * gdb_sysroot is set and not remote.
>
> This logic is skipped for remote gdb_sysroots because the subsequent
> code does not support opening the main executable over the remote
> protocol. This is something I intend to rectify with future patches
> but the ability to use gdb_sysroot like this is useful for attaching
> to processes running in chroot jails and containerized environments
> so I am submitting this series independently.
>
> Built and regtested on RHEL 6.6 x86_64.
>
> Ok to commit?
What problem are you trying to fix?
next prev parent reply other threads:[~2015-03-05 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 11:37 Gary Benson
2015-03-05 11:37 ` [PATCH 2/2] Use exec_file_find to locate executable on attach (sometimes) Gary Benson
2015-03-05 11:37 ` [PATCH 1/2] Introduce new function exec_file_find Gary Benson
2015-03-05 12:49 ` Mark Kettenis [this message]
2015-03-05 13:39 ` [PATCH 0/2] Use gdb_sysroot for main executable on attach Gary Benson
2015-03-12 11:44 ` [PING][PATCH " Gary Benson
2015-03-18 15:22 ` [PATCH " Gary Benson
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=201503051248.t25CmnZH014990@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
/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