From: "Ken Moore" <KMoore@gse-inc.com>
To: <karuottu@freenet.hut.fi>
Cc: <insight@sourceware.cygnus.com>
Subject: Re: getting older versions of insight
Date: Fri, 30 Jun 2000 11:33:00 -0000 [thread overview]
Message-ID: <s95caf7c.034@ait-udi.com> (raw)
Kai,
We have a version of insight (v4.18, mingw build, targeted to 68k-elf) which is supposed to have come from your site. The problem with the version is it did not allow you to stop the code via the stop button (you had to hit a breakpoint). I am told there is a patch for this version that would fix this issue. Therefore, I am trying to find this older version and patch, and get them working. If you can offer any assistance, or are interested in doing it yourself (in which case we can talk more), that would be great.
Ken
>>> Kai Ruottu <karuottu@freenet.hut.fi> 06/29/00 05:18PM >>>
Ken Moore wrote:
>
> I have seen that older versions of gdb (ie v4.18, v4.2, v4.6 etc) are available on the cygnus site.
> I do not see corrosponding older versions of insight. Do they exist, and is there anywhere to get
> them?
Insight used to be a proprietary product before July 27, 1999, although being 'derived from GDB'.
But some Cygnus customers have released the sources, Hitachi being one. So you can now get the
'GNUPro-98r2' sources with Insight included on their free "Electronic Databook 2000" CDROM, or
download the 'GNUPro-99r1p1' sources in a near 100 M package with prebuilt H8/300 or SH tools.
Also the RedHat EDK sources include the 'Insight-4.18-000221'.
Cheers, Kai
next reply other threads:[~2000-06-30 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-30 11:33 Ken Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-29 6:36 Ken Moore
2000-06-29 15:47 ` Kai Ruottu
2000-06-29 6:20 Ken Moore
2000-06-29 6:26 ` Mo DeJong
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=s95caf7c.034@ait-udi.com \
--to=kmoore@gse-inc.com \
--cc=insight@sourceware.cygnus.com \
--cc=karuottu@freenet.hut.fi \
/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).