public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Hans Kester <kester.hans@gmail.com>
Cc: insight@sourceware.org
Subject: Re: Insight 6.8
Date: Mon, 31 Mar 2008 19:15:00 -0000	[thread overview]
Message-ID: <47F13788.6000402@redhat.com> (raw)
In-Reply-To: <93da74750803310225v1cbf162bn2d1a7af1edebd8e2@mail.gmail.com>

Hans Kester wrote:

> 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.

This is odd. Can you open a console window and type "list main"? Does it 
show the code? For some reason, Insight cannot find the source code. Can 
you try opening a debug window?

> 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.

Insight suddenly disappearing is undoubtedly a crash. I wouldn't be 
surprised if the architecture change wasn't properly recorded/noticed by 
Insight's various windows. To find the location of the crash, can you 
repeat this while running insight on gdb?

Keith

  reply	other threads:[~2008-03-31 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31  9:25 Hans Kester
2008-03-31 19:15 ` Keith Seitz [this message]
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=47F13788.6000402@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sourceware.org \
    --cc=kester.hans@gmail.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).