public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Kai Ruottu <karuottu@freenet.hut.fi>
To: Paul_Heijman@eu.omron.com
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight exits abrupt when trying to view in ASM or MIXED mode.
Date: Fri, 19 May 2000 04:05:00 -0000	[thread overview]
Message-ID: <392520F1.CA03731@freenet.hut.fi> (raw)
In-Reply-To: <412568E3.0031EADC.00@eu.omron.com>

Paul_Heijman@eu.omron.com wrote:
> 
> Does this sound familiar to anyone:
> 
> I am using Insight to remote-debug a 68000 microcontroller.
> Almost everything works perfect. After loading the .cof file into GDB, I can
> step through the (C) source code.
> When I try to view the ASSEMBLY code (in ASSEMBLY or MIXED view mode),
> Insight closes without any error message!
> 
> I have seen the assembly / mixed mode view working earlier, but then I
> wasn't able to view the C source code. I think I solved it by upgrading
> to a newer version of cygwin1.dll.

 This 'feature' isn't related to only Cygwin, also the Linux and Mingw hosts
have had problems (probably all hosts). I found first the 'mips64*' targets
not being able to show the assembly... This is really a '2k'-problem, when
it appeared during December-1999 - January-2000... Later it started to show
with all targets somehow... But normally one sees only that single-stepping
in the 'src+asm' display doesn't update the display... Not as bad as you
have described... BTW, I reported this problem with the 'mips64*' targets
in January-February in this maillist. No response from anyone, so if I'll
find a cure for it, perhaps there is no reason to tell anyone else but you,
when this 'feature' doesn't seem to hurt anyone else but me and you...

 I really will try to fix these problems with the assembly not showing with
the 'mips64*' targets and the single-stepping not updating the display with
any targets... But it may take some time, because I just haven't cared if the
current snapshots work or not, when the older ones do work... But adopting
new things from the new sources to the old working sources has started to
be quite hard...

> I now have tried several latest versions of the DLL, but it doesn't make a
> difference.Does anyone know of a solution?

 I have stayed using the '19991116'-snapshots, (sometimes spying if the
current snapshots have cured the 'features' -- the '20000425' and '20000502'
ones at least weren't...). To get the single-stepping to work, I had to
take still older scripts (19990727) in use...

 BTW, you could try my downloadable 'm68k-elf' and 'm68k-palmos-coff'
Insights for the Mingw host... They are gdb-4.18-based, and if I don't
remember it wrong, someone recently claimed it being impossible to build
gdb-4.18 based Insights, and also the Mingw-host has been doomed as
impossible for a long time... But perhaps I'm too stupid to believe when
the 'wise' men claim these things... Not knowing any better, I even dared
to build ten or more Win3.1x/Win32s-hosted Insights (What a sin this must
be...). Ok, please see ' http://www.saunalahti.fi/~ankosk2/embtools.htm '...

Cheers, Kai

  parent reply	other threads:[~2000-05-19  4:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-18  1:12 Paul_Heijman
2000-05-18  5:42 ` Keith Seitz
2000-05-19  4:05 ` Kai Ruottu [this message]
     [not found] <412568E3.005B3A0E.00@eu.omron.com>
2000-05-18  8:55 ` Keith Seitz

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=392520F1.CA03731@freenet.hut.fi \
    --to=karuottu@freenet.hut.fi \
    --cc=Paul_Heijman@eu.omron.com \
    --cc=insight@sourceware.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).