From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Dubuc <pdubuc@cas.org>
Cc: GDB Mailing List <gdb@sources.redhat.com>
Subject: Re: GDB and compiler version.
Date: Fri, 26 Sep 2003 18:40:00 -0000 [thread overview]
Message-ID: <20030926183948.GB8920@nevyn.them.org> (raw)
In-Reply-To: <3F74817B.3080704@cas.org>
On Fri, Sep 26, 2003 at 02:12:11PM -0400, Paul Dubuc wrote:
> We are using gdb with the GCC C++ compiler on Solaris. Recently we
> upgraded GCC
> from 2.95.3 to 3.3.1 and gdb from 5.0 to 5.3. We also upgraded binutils
> 2.11 to
> 2.14.
>
> My question is Are there any compiler or binutils dependencies in gdb?
> Should
> gdb 5.3 compiled with g++ 3.3.1 work as well on code that is compiled with
> g++
> 2.95.3? Or do I always need to use a gdb that is built with the same
> version of
> GCC that is used to build the programs it debugs?
It should not matter.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-26 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 18:17 Paul Dubuc
2003-09-26 18:40 ` Daniel Jacobowitz [this message]
2003-09-26 21:56 Michael Elizabeth Chastain
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=20030926183948.GB8920@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=pdubuc@cas.org \
/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