From: Roland Schwingel <roland@onevision.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Don't enable gdbtk in testsuite
Date: Fri, 05 Dec 2014 11:27:00 -0000 [thread overview]
Message-ID: <54819675.9040501@onevision.com> (raw)
Hi...
> FWIW - I was hoping insight would be dead by now, but if people
> still use it and make updates, then I wouldn't be opposed either.
> The one thing to be careful of, I think, is handling of their
> commits. Probably just a third email list for insight-specific
> files?
No it is not dead.
Well at least here insight is in active use. A self built version with
gdb 7.7 presently... I know I need to update... It is used as native
mingw-w64 version (NOT CYGWIN) to debug 32bit and 64bit mingw
windows executables. Also it is in use on linux for debugging
64bit linux executables.
I know Insight is in some kind of stasis but please don't kill it.
I believe its time is still not over.
A new final official place would be great. Presently I am very
thankful to Patrick Monnerat for his git repo. But solving this
repo blockade and having a final new home for insight would be best.
(Plus some again active development on Insight ... ;^)
Thanks,
Roland
next reply other threads:[~2014-12-05 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 11:27 Roland Schwingel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-25 8:11 Yao Qi
2014-11-30 15:23 ` Joel Brobecker
2014-12-01 6:15 ` Yao Qi
2014-12-04 17:07 ` Pedro Alves
2014-12-05 6:55 ` Yao Qi
2014-12-05 9:54 ` Pedro Alves
2014-12-05 10:05 ` Joel Brobecker
2014-12-05 12:04 ` Yao Qi
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=54819675.9040501@onevision.com \
--to=roland@onevision.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).