From: Evan Lavelle <anti.spam1@dsl.pipex.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: Arthur Prosso <arthur@altiris.ee>,
"insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight-5.3 hangs
Date: Mon, 27 Oct 2003 19:54:00 -0000 [thread overview]
Message-ID: <3F9D77D9.6080409@dsl.pipex.com> (raw)
In-Reply-To: <1067281401.2370.15.camel@dragon>
Martin M. Hunt wrote:
> On Mon, 2003-10-27 at 00:49, Arthur Prosso wrote:
>
>>Hello.
>>I have downloaded insight-6.0, as you recommended.
>>Compilation and Installation succeeded.
>>At run time there are exactly the same problems as with insight-5.3 (see mail below)
>>Please note again, that I used gcc-3.2.3 for insight compilation (the same version
>>of compiler was used for building the test application being debugged by insight).
>>
>>What is the recommended version of gcc for insight compilation?
>
>
> Any version should work fine. You said you already built it. There is
> no need to use the same versions of gcc to build Insight and the
> application being debugged.
My recollection is that Insight 6.0, compiled on gcc 3.3, can't be used
to debug binaries compiled with 2.96. I forget what the problem was -the
console window showed an error message when loading the 2.96 executable.
Was there some change in symbol meanings between gcc 2.96 and 3.3?
Evan
next prev parent reply other threads:[~2003-10-27 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 8:49 Arthur Prosso
2003-10-27 19:03 ` Martin M. Hunt
2003-10-27 19:54 ` Evan Lavelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 9:02 Arthur Prosso
2003-10-22 9:41 ` Martin M. Hunt
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=3F9D77D9.6080409@dsl.pipex.com \
--to=anti.spam1@dsl.pipex.com \
--cc=arthur@altiris.ee \
--cc=hunt@redhat.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).