public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <kseitz@firetalk.com>
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: Thu, 18 May 2000 05:42:00 -0000	[thread overview]
Message-ID: <3923E53F.8E3F1748@firetalk.com> (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!
> 

When you say that you load the ".cof" file, are you loading symbols only
or the executable with symbols? (Are you using Insight's
File->Open/console window's "file" command or using the console command
"add-symbol-file"?)

For the record, let me say (just to warn anyone out there), NEVER use
just the "add-symbol-file" command without ever having used the "file"
command (or File->Open). The problem that ofter arises in Insight
involves disassembling memory. Specifically, Insight does not access
memory on a non-native target the same way that gdb does.

Gdb will always access memory from the executable file UNLESS you're
attached to a target (with the "target" command or its equivalent in
gui-land). When you're attached, gdb will read memory from the actual
target. ALL memory accesses, including disassembly, occur this way.

Insight/gdbtk, on the other hand, will almost always access memory from
the executable on non-native targets. This was added to aid developers
using remote targets with slow communications facilities (like a 9600
baud serial line using a monitor -- yich!).

So, you already state that all disassembly isn't working, so that's a
strong hint that something like this may be happening (gdbtk cannot get
at the memory or something). Can you disassemble BEFORE attaching
(again, ASSEMBLY mode or from console window)?

What version of gdbtk are you using? (Type "show version" in console
window or run "gdb -v".)

Keith
-- 
Why chat when you can Firetalk?
Firetalk ID: Keith (10320)
www.firetalk.com

  reply	other threads:[~2000-05-18  5:42 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 [this message]
2000-05-19  4:05 ` Kai Ruottu
     [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=3923E53F.8E3F1748@firetalk.com \
    --to=kseitz@firetalk.com \
    --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).