public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Dave Murphy <wintermute2k4@ntlworld.com>
To: insight@sources.redhat.com
Subject: Re: Insight on Cygwin : GUI is not showing up
Date: Fri, 30 Sep 2005 15:21:00 -0000	[thread overview]
Message-ID: <433D57AA.6060005@ntlworld.com> (raw)
In-Reply-To: <433C67DC.4070209@sakuraindustries.com>

Accounts wrote:

> Hi Dave,
>
> You do know that Insight is still in the GDB CVS Tree dont you?


yep :)

> Also, the Insight website has some recent CVS Snapshots, which should 
> build OK.


Unfortunately CVS head doesn't currently build under msys/mingw. I've
got plain vanilla gdb to build with minimal patching but adding Insight
is still a little problematic, not far off though. I just need to figure
out why the gdbtk module isn't picking up the tcl headers and I think it
should be plain sailing from there.

> That might be a lot easier than trying to take the insight code from 
> 6.1 and inject it onto GDB6.3 (without insight).  There have been a 
> number of patches since then (just no official release).
>
I actually did this the other way round, injecting gdb 6.3 into the
Insight 6.1 tree, it's fairly easy to do although the patches aren't
exactly trivial. It was really just a matter of checking out the 6.1
tree, bringing the gdb sections up to 6.3 then applying a patch
generated from the mingw gdb source, Andrew's SEH fix and a couple of
minor configury changes.

Dave


      reply	other threads:[~2005-09-30 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 18:36 a.fink
2005-09-29 19:08 ` Dave Murphy
2005-09-29 22:17   ` Accounts
2005-09-30 15:21     ` Dave Murphy [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=433D57AA.6060005@ntlworld.com \
    --to=wintermute2k4@ntlworld.com \
    --cc=insight@sources.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).