Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
	GDB Patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH/RFC] Implement the ability to set the current working directory in GDBserver
Date: Thu, 31 Aug 2017 22:01:00 -0000	[thread overview]
Message-ID: <79779c39-8f54-c5da-5450-e67a35294e08@redhat.com> (raw)
In-Reply-To: <20170830043811.776-1-sergiodj@redhat.com>

On 08/30/2017 06:38 AM, Sergio Durigan Junior wrote:
> I didn't want to implement a gdbserver-specific command (e.g., "set
> remote directory"), which means that my approach has some drawbacks.
> For example, if you want gdbserver to cd to "/abc", but "/abc" doesn't
> exist in the host, then you still won't be able to do this, because
> GDB obviously won't allow you to "cd" into a non-existing dir.  So you
> will have to have the same directory structure in both host and target
> if you want to do that.

I'm not sure this is the right approach.  I'd like to have a
better understanding of what are the use cases "cd" is used for.
Beyond affecting the inferior's cwd when it is started, what
else is/can "cd" used for?  Or IOW, what else does GDB's
current working directory affect?

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-08-31 22:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  4:38 Sergio Durigan Junior
2017-08-30 14:29 ` Eli Zaretskii
2017-08-31 21:41   ` Sergio Durigan Junior
2017-09-01 12:32     ` Philippe Waroquiers
2017-09-01 18:40       ` Sergio Durigan Junior
2017-08-31 22:01 ` Pedro Alves [this message]
2017-08-31 22:42   ` John Baldwin
2017-09-05 17:45   ` Sergio Durigan Junior
2017-09-06 14:20     ` Pedro Alves
2017-09-06 18:18       ` Sergio Durigan Junior

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=79779c39-8f54-c5da-5450-e67a35294e08@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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