Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] New option -B: simplify running gdb from build directory
Date: Fri, 27 Dec 2013 20:15:00 -0000	[thread overview]
Message-ID: <838uv63vav.fsf@gnu.org> (raw)
In-Reply-To: <yjt2lhz6t716.fsf@ruffy.mtv.corp.google.com>

> From: Doug Evans <dje@google.com>
> Date: Fri, 27 Dec 2013 11:42:29 -0800
> 
> The "make run" Makefile rule simplifies running gdb from the shell,
> but it doesn't simplify running gdb from gdb: I'm always typing
> "--data-directory=$(pwd)/data-directory".
> And since we can't agree on a way to let gdb auto-detect being run
> from the build directory, how about this?

Thanks.

However, if we cannot agree on the above, why would adding a new
option facilitate agreement?

Personally, this way of solving the issue makes little sense to me: if
I need to specify a special option to GDB, I can be expected to
specify --data-directory explicitly.


  parent reply	other threads:[~2013-12-27 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 19:42 Doug Evans
2013-12-27 19:54 ` Doug Evans
2013-12-27 20:15 ` Eli Zaretskii [this message]
2013-12-27 20:51   ` Doug Evans
2014-03-06 21:41 ` [PATCH, doc RFA] " Doug Evans
2014-03-07  7:10   ` Eli Zaretskii
     [not found]     ` <CADPb22RKaBx1p2vF4-wGODZVe-QqdGc93Ax-bD82xb9Adr5EJw@mail.gmail.com>
2014-03-07 18:41       ` Eli Zaretskii
2014-03-07 18:54         ` Doug Evans
2014-03-25  1:02           ` Doug Evans
2014-03-25  1:20             ` Doug Evans
2014-03-25  1:28               ` Doug Evans
2014-04-28 22:35                 ` [PATCH, doc RFA] New option -D: alias for --data-directory Doug Evans
2014-04-29  2:37                   ` Eli Zaretskii
2014-05-16 19:17                     ` Doug Evans

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=838uv63vav.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.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