From: "Hans Kester" <kester.hans@gmail.com>
To: "Keith Seitz" <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Insight 6.8
Date: Thu, 03 Apr 2008 13:19:00 -0000 [thread overview]
Message-ID: <93da74750804030618u2fd40cbej371471c17c373c36@mail.gmail.com> (raw)
In-Reply-To: <47F3C17D.3080801@redhat.com>
Keith Seitz <keiths@redhat.com> wrote:
>
> > "list main" shows the correct source code. I can also select any
> > source file in the source window and I get the full source. It looks
> > like it only doesn't display the source once at startup. Weird!
> >
>
> That is very confusing. So let me see if I understand what's happening...
> You start up insight, load an executable file, and insight cannot show the
> entry point -- the source window is blank. When you attach to a target (and
> download?), the source is then displayed properly in the source window.
I don't get a blank source window but a window with disassembly from
main(). This main() function is in the file App.cpp. If I manually
select the same file from the drop down list in the source window I
suddenly get the C++ source. So only the very first time I get
disassembly, the next time the source file is loaded I get source
code.
> It sounds like there is a problem finding the entry point (which is what
> insight attempts to show before there is a register set). When you start up
> (and the source window is blank), open a console window and enter the
> command "tk gdbtk_locate_main". What is the result?
(gdb) tk gdbtk_locate_main
../MasterX86/App.cpp main ../MasterX86/App.cpp 33 0x041004f4 0x00000000 {}
So that's not the problem...
next prev parent reply other threads:[~2008-04-03 13:19 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
2008-04-01 10:41 ` Hans Kester
2008-04-02 17:28 ` Keith Seitz
2008-04-03 13:19 ` Hans Kester [this message]
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=93da74750804030618u2fd40cbej371471c17c373c36@mail.gmail.com \
--to=kester.hans@gmail.com \
--cc=insight@sourceware.org \
--cc=keiths@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).