public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Masahide Tomita" <fsi_tomi@bcpc601.neec.abk.nec.co.jp>
To: <insight@sources.redhat.com>
Subject: Re: Which version with JEENI?
Date: Wed, 30 Oct 2002 04:29:00 -0000	[thread overview]
Message-ID: <003a01c28010$06f50c30$41dc280a@ABKNEECBCPCD65> (raw)
In-Reply-To: <4.3.2.7.2.20021030133836.00b68b80@vttmail.vtt.fi>

Hi Harri,

I'm using (actually, just started using them) GDB 5.0 (20010428-3) on Cygwin
1.3.12, but so far none of error messages or whatsoever showed up.
Possibly, as you mentioned, it's snapshot bug.

My platform is i686-pc-cygwin (on WinXP), and I chose everything when I
install Cygwin, for your infomation.

--

Masahide Tomita

fsi_tomi@bcpc601.neec.abk.nec.co.jp

----- Original Message -----
From: <harri.siirtola@vtt.fi>
To: <insight@sources.redhat.com>
Sent: Wednesday, October 30, 2002 8:38 PM
Subject: Which version with JEENI?


> Hi,
>
> I just started using Insight after purchasing a JEENI. Back when I
> installed Cygwin and other GNU tools, I seem to have downloaded the
> 20010523 snapshot of GDB (same for Insight?). It works quite well but I
> can't use memory window preferences. I get 'Error: bad window path name
> "::.memwin().memwin"' and am stuck with dword display.
>
> So, as I need this functionality, I suppose it's best to get the most
> reliable version as I'm into it.
>
> Please give the best combination if possible. My platform is:
>
> WIN98 (host=i586-pc-cygwin)
> Cygwin 1.3.2
> GDB (and Insight?) 20010523
> target ARM-ELF
>
> TIA,
>
> Harri
>
>
>


  reply	other threads:[~2002-10-30 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  3:44 harri.siirtola
2002-10-30  4:29 ` Masahide Tomita [this message]
2002-10-30  4:50   ` Tim Chick
2002-11-01  1:02 harri.siirtola
2002-11-01 11:36 ` Grant Edwards
2002-11-04  3:52 harri.siirtola
2002-11-04  8:20 ` Grant Edwards

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='003a01c28010$06f50c30$41dc280a@ABKNEECBCPCD65' \
    --to=fsi_tomi@bcpc601.neec.abk.nec.co.jp \
    --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).