From: Simon Sobisch <simonsobisch@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: gdbtk ...completely broken?
Date: Wed, 27 Jul 2022 17:09:54 +0200 [thread overview]
Message-ID: <78365004-54cb-4602-bbd7-3d88064667a4@gnu.org> (raw)
In-Reply-To: <66c1653d-aae0-4d39-f58e-5fcb1cdf60ed@redhat.com>
Am 27.07.2022 um 16:14 schrieb Keith Seitz:
> 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.
Ah - I'd say there was a near zero chance to even guess that.
Could you please try to add notes about this in gdb's configure.ac (a
note on --enable-gdbtk about both the project Insight and about "only
for using GDB as Insight submodule" - would help a lot) and possibly on
GDBs mode options docs (something along "-w start GDB in GUI mode
(Insight)") and help output, too?
>
>> Where are the necessary source files?
>
> Clone sourceware.org/git/insight.git and follow the README. It uses
> submodules
> to pull in binutils-gdb.
How to get the files without git (newest insight + GDB [12.1] I've
already on the harddisk)? Is the build info [1] still up-to-date that I
need to build it with a specific tcl/tk version?
https://sourceware.org/insight/downloads.php seems to be quite outdated,
too (ftp links don't work here, instead of git web frontend it points to
cvs)
>> 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.
Thanks, just checking for the necessary source files (before even
checking tcl/tk), then abort looks most reasonable to me.
I guess this is all rooted in the mentioned TODO 2
> Get Insight integrated and accepted into the GDB mainline.
Question on that: Is it likely that this will happen someday?
> I'll put it on my TODO list.
>
> Keith
Thanks again for taking the time to answer!
Simon
[1]: https://sourceware.org/insight/faq.php#q-2.1
prev parent reply other threads:[~2022-07-27 15:10 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
2022-07-27 15:09 ` Simon Sobisch [this message]
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=78365004-54cb-4602-bbd7-3d88064667a4@gnu.org \
--to=simonsobisch@gnu.org \
--cc=gdb@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).