Philip Blundell writes:
> The binaries have to be built in some directory, and whatever pathname
> is used will end up embedded in the debug information. There's not a
> lot we can do about this.
therefore closing the repot. adding a paragraph about debugging
libstdc++ for the next upload.
--
On Mon, Jun 10, 2002 at 09:03:14AM -0400, Phil Edwards wrote:
> On Mon, Jun 10, 2002 at 02:15:35PM +0200, Ulrich Eckhardt wrote:
> > While trying to debug a program, I encountered some weird paths that
> > prevented me from taking advance of the debug-lib:
> >
> > LD_PRELOAD=/usr/lib/libstdc++_de
On Mon, Jun 10, 2002 at 02:15:35PM +0200, Ulrich Eckhardt wrote:
> While trying to debug a program, I encountered some weird paths that
> prevented me from taking advance of the debug-lib:
>
> LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++3.so.3 gdb ./test
> ...
> (gdb) step
> 178 in
> /home/
On Mon, 2002-06-10 at 13:15, Ulrich Eckhardt wrote:
> Package: libstdc++3-dbg
> Version: 3.0.4-7
>
> While trying to debug a program, I encountered some weird paths that
> prevented me from taking advance of the debug-lib:
>
> LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++3.so.3 gdb ./test
> ...
Package: libstdc++3-dbg
Version: 3.0.4-7
While trying to debug a program, I encountered some weird paths that
prevented me from taking advance of the debug-lib:
LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++3.so.3 gdb ./test
...
(gdb) step
178 in
/home/doko/packages/gcc/3.0/gcc-3.0-3.0.4ds3/
5 matches
Mail list logo
