This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.1 and gdb 5.2?
- From: Joe Buck <Joe dot Buck at synopsys dot com>
- To: doug at ikos dot com (Doug Warmke)
- Cc: dylan at q-games dot com, gcc at gnu dot org, robt at flyingpig dot com,arnabs at ikos dot com, doug at ikos dot com, johnny at ikos dot com, vasu at ikos dot com,tich at ikos dot com
- Date: Thu, 13 Jun 2002 14:31:33 -0700 (PDT)
- Subject: Re: gcc 3.1 and gdb 5.2?
> We are stuck after a variety of experiments.
> We tried gdb 5.1.1 and gdb 5.2, and we used
> the latest gnu ld from binutils-2.12.
>
> When using gdb 5.2, setting a breakpoint in
> gdb results in immediate core dump.
>
> When using gdb 5.1.1, setting a breakpoint
> takes effect, but when we try to run, we
> get a message about libstdc++.so.4: open failed.
> This in spite of every possible manipulation
> of $LD_LIBRARY_PATH. Some transcript
> exists below to show what's happening.
>
> Looks like we'll have to give up on using gcc 3.1
> on Solaris until someone makes a breakthrough
> with gdb.
>
> Thanks for your help and advice.
A couple of things to try:
- use -gstabs to get stabs-style debugging code.
As for your other problem: you may be bitten by a gdb misfeature if you
use csh or tcsh; it will source your .cshrc, wiping out your
LD_LIBRARY_PATH setting if you set it from .cshrc. One workaround for
csh/tcsh users is something like
env SHELL=/bin/sh gdb [arguments]