public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Hans Kester" <kester.hans@gmail.com>
To: insight@sourceware.org
Subject: Insight 6.8
Date: Mon, 31 Mar 2008 09:25:00 -0000	[thread overview]
Message-ID: <93da74750803310225v1cbf162bn2d1a7af1edebd8e2@mail.gmail.com> (raw)

After building two versions of Insight I have some issues. I am using
Cygwin 1.5.25 on Windows XP Professional (32-bit). I used
"--target=i686-elf --disable-nls" for the first debugger and
"--target=x86_64-pc-linux --disable-nls" for the second.

Issue 1:
When I open my ELF-file Insight only shows me assembly code, not the
C++ source code. After reselecting the same ELF-file I do get source
code. We also get source code after downloading and running the
program. This happens with both debuggers and it still worked in
Insight 6.7.1.

Issue 2:
When I start the debugger for the 64-bit target, it starts in 32-bit
target mode. When I open the register window I only see the 32-bit
registers. After selecting the 64-bit ELF-file the register window
does not switch to the 64-bit register set. After closing and
reopening the register window I do get the 64-bit register set. I can
download and run the program without any problems until I stop the
program and open the register window again. Insight disappears without
an error or warning. It looks to me that it didn't switch to the
64-bit architecture completely. It works with Insight 6.6 but not with
6.7.1.

Any ideas?

Hans Kester

             reply	other threads:[~2008-03-31  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31  9:25 Hans Kester [this message]
2008-03-31 19:15 ` Keith Seitz
2008-04-01 10:41   ` Hans Kester
2008-04-02 17:28     ` Keith Seitz
2008-04-03 13:19       ` Hans Kester
2008-04-03 13:34         ` Hans Kester

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=93da74750803310225v1cbf162bn2d1a7af1edebd8e2@mail.gmail.com \
    --to=kester.hans@gmail.com \
    --cc=insight@sourceware.org \
    /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).