From: "Kip Warner" <Kip@thevertigo.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Insight Bug?
Date: Sun, 03 Oct 2004 03:12:00 -0000 [thread overview]
Message-ID: <opse9xvovze8k94p@mail.thevertigo.com> (raw)
Greetings,
I have tried using two different MinGW builds of Insight only to find that
neither can view source mode of my GCC produced executables. All I can see
is assembly listing. I am compiling with -g3, full debugging information
and I am not stripping them with the linker. Any ideas?
--
Kip Warner
Vertigo
http://TheVertigo.com
next reply other threads:[~2004-10-03 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 3:12 Kip Warner [this message]
2004-10-03 3:43 ` Keith Seitz
[not found] <opsfi9s0h3e8k94p@mail.thevertigo.com>
2004-10-08 14:29 ` Keith Seitz
[not found] ` <opsfn5rmzge8k94p@mail.thevertigo.com>
2004-10-10 19:40 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2000-05-29 6:32 Paul_Heijman
2000-05-29 8:12 ` Fernando Nasser
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=opse9xvovze8k94p@mail.thevertigo.com \
--to=kip@thevertigo.com \
--cc=insight@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: 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).