public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: "Kip Warner" <Kip@thevertigo.com> To: kseitz@sources.redhat.com Cc: insight-prs@sources.redhat.com, Subject: Re: insight/274: Insight cannot show source in source view Date: Sat, 19 Nov 2005 22:53:00 -0000 [thread overview] Message-ID: <20051119225301.8054.qmail@sourceware.org> (raw) The following reply was made to PR insight/274; it has been noted by GNATS. From: "Kip Warner" <Kip@thevertigo.com> To: insight-gnats@sources.redhat.com Cc: Subject: Re: insight/274: Insight cannot show source in source view Date: Sat, 19 Nov 2005 14:43:03 -0800 Nope, it doesn't look like a GDB bug. I understand that Insight is just the frontend for GDB, but I think there are still complications in the way it is communicating with it. Look at this pic: http://thevertigo.com/temp/thing2.png The console on the upper left side is my binary running under gdb.exe. I am able to "list" source no problem. The other windows is the same binary running under Insight. Every source code module can be listed only as an assembly listing. If I open the console dialog box in Insight and enter "list", it fails to work. To execute gdb or insight on my program, I run the following: "C:\Dev\Debuggers\Insight\MinGW GDB 6.3.50\bin\gdb.exe" --readnow --se="C:\Projects\Agni\dist\bin\aa.exe" --directory="C:\Projects\Agni\src\AgniAssembler\" Where "gdb.exe" can be replaced with "insight.exe" to run the GUI instead. Hope that helps. -- Kip Warner Vertigo http://TheVertigo.com
next reply other threads:[~2005-11-19 22:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-19 22:53 Kip Warner [this message] -- strict thread matches above, loose matches on Subject: below -- 2005-11-19 16:33 kseitz 2005-11-12 10:43 Kip Warner 2005-11-11 23:03 Kip Warner 2005-11-11 23:03 Kip Warner 2005-11-11 17:27 kseitz 2005-09-25 20:13 Kip Warner 2005-09-25 20:03 Kip
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=20051119225301.8054.qmail@sourceware.org \ --to=kip@thevertigo.com \ --cc=insight-prs@sources.redhat.com \ --cc=kseitz@sources.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: linkBe 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).