From: Keith Seitz <keiths@redhat.com>
To: Simon Sobisch <simonsobisch@gnu.org>, gdb@sourceware.org
Subject: Re: gdbtk ...completely broken?
Date: Wed, 27 Jul 2022 07:14:31 -0700 [thread overview]
Message-ID: <66c1653d-aae0-4d39-f58e-5fcb1cdf60ed@redhat.com> (raw)
In-Reply-To: <48ec6c7a-8e6c-0163-f354-584e8084e595@gnu.org>
On 7/26/22 01:07, Simon Sobisch via Gdb wrote:
> After checking gdb --help I've wondered about the following:
>
> -w Use the GUI interface.
> --nw Do not use the GUI interface.
>
> it took a while to find out that `-w` only applies if GDB is configured with the GUI option and much more that this relates to --enable-gdbtk.
"gdbtk" refers to Insight, which is now located in a different GIT repository.
> Where are the necessary source files?
Clone sourceware.org/git/insight.git and follow the README. It uses submodules
to pull in binutils-gdb.
> Should gdb's configure assume they exist or test for them (and again: error on --enable-gdbtk)?
That's probably something that needs better documentation and perhaps the error.
I'll put it on my TODO list.
Keith
next prev parent reply other threads:[~2022-07-27 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 8:07 Simon Sobisch
2022-07-27 14:14 ` Keith Seitz [this message]
2022-07-27 15:09 ` Simon Sobisch
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=66c1653d-aae0-4d39-f58e-5fcb1cdf60ed@redhat.com \
--to=keiths@redhat.com \
--cc=gdb@sourceware.org \
--cc=simonsobisch@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).