From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: khooyp@cs.umd.edu, jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Warn about data-directory when failing to import Python "gdb" module
Date: Tue, 18 Sep 2012 06:17:00 -0000 [thread overview]
Message-ID: <83txuv26ti.fsf@gnu.org> (raw)
In-Reply-To: <20120917205828.GA28626@adacore.com>
> Date: Mon, 17 Sep 2012 13:58:29 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, GDB Patches <gdb-patches@sourceware.org>
>
> > If you are running GDB from the build directory, please run gdb with
> > the -data-directory flag set as appropriate, e.g., "builddir/gdb
> > -data-directory builddir/data-directory".
>
> I expect that the majority of users will *not* be running GDB out
> of the build directory. If they encounter the same issue with a
> poorly installed GDB (Eg: They copied the GDB binary from one location
> to another without copying the remaining support files), the error
> message is not going to help them.
>
> I think that people who do run GDB from the build directory (a power
> user setup) should be sufficiently knowledgeable, and we should try
> to tailor the hints towards regular users.
Is it possible to make GDB find its data-directory when it is run from
the directory where it was built?
next prev parent reply other threads:[~2012-09-18 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 19:36 Khoo Yit Phang
2012-09-17 20:23 ` Jan Kratochvil
2012-09-17 20:28 ` Khoo Yit Phang
2012-09-17 20:36 ` Jan Kratochvil
2012-09-17 20:58 ` Joel Brobecker
2012-09-17 21:04 ` Khoo Yit Phang
2012-09-18 20:40 ` Khoo Yit Phang
2012-09-22 13:30 ` Jan Kratochvil
2012-09-22 18:37 ` Khoo Yit Phang
2012-10-06 20:56 ` Ping! " Khoo Yit Phang
2012-09-18 6:17 ` Eli Zaretskii [this message]
2012-09-18 11:58 ` Jan Kratochvil
2012-09-18 12:21 ` Eli Zaretskii
2012-09-18 13:54 ` Joel Brobecker
2012-09-18 15:38 ` Khoo Yit Phang
2012-09-18 15:44 ` Jan Kratochvil
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=83txuv26ti.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=khooyp@cs.umd.edu \
/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