public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: James Ingham <jingham@cygnus.com>
Cc: "M.A. Henderson" <dchender@esn.net>, insight@sourceware.cygnus.com
Subject: Re: Mingw32
Date: Wed, 18 Aug 1999 11:47:00 -0000	[thread overview]
Message-ID: <199908181847.NAA08146@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <14266.65180.195353.24648@leda.cygnus.com>

James Ingham <jingham@cygnus.com> writes:
> 
> Gdb uses a whole bunch of Cygwin functionality to do its job on
> Windows, and there are currently no plans to rewrite these sections to
> call directly into the Windows API.  That would be a pretty big job,
> with no clear payoff.  So, no, a Mingw32 version of Insight is not
> likely to happen.
> 

Actually, I've had a mingw port for a few years now. It requires a few
simple changes to gdb (win32-nat.c and the config files). The problem
is readline -- the older version had a "minimal" mode, but not available
anymore, and I have to essentially use a older version of readline to
get the job done. For mingw diffs to gdb-4.1[78], see:

  ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/ports/

I haven't had the time to write up ChangeLog entries, but it's pretty
self-explanatory. When I get some time, I'll clean up the patches and
submit (and there's the assignment issue I keep on forgetting about). 

Unless the internals of gdb in insight is quite different and somehow
uses other Cygwin functionality, it should work.  Of course, lots of
mingw-specific tcl/tk changes are probably not in the Cygnus tree,
so that may involve some work.

Regards,
Mumit

  reply	other threads:[~1999-08-18 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-18 11:25 Mingw32 M.A. Henderson
1999-08-18 11:40 ` Mingw32 James Ingham
1999-08-18 11:47   ` Mumit Khan [this message]
1999-08-18 11:58     ` Mingw32 James Ingham
1999-08-18 12:02       ` Mingw32 Mumit Khan
1999-08-18 12:16         ` Mingw32 James Ingham
1999-08-18 12:35           ` Mingw32 Mumit Khan
1999-08-18 11:41 ` Mingw32 Mumit Khan

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=199908181847.NAA08146@mercury.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=dchender@esn.net \
    --cc=insight@sourceware.cygnus.com \
    --cc=jingham@cygnus.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).