Bug#149561: marked as done (bad pathnames coded into the libs)
Your message dated Sat, 16 Nov 2002 13:52:00 +0100 (MET)
with message-id <200211161252.gAGCq0N05399@bolero.cs.tu-berlin.de>
and subject line really close #149561
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Jun 2002 12:16:08 +0000
>From uli@doommachine.dyndns.org Mon Jun 10 07:16:08 2002
Return-path: <uli@doommachine.dyndns.org>
Received: from b080075.adsl.hansenet.de (monolith.base42.lan) [62.109.80.75]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17HO5g-0001nd-00; Mon, 10 Jun 2002 07:16:08 -0500
Received: from uli by monolith.base42.lan with local (Exim 3.35 #1 (Debian))
id 17HO5A-0002C3-00
for <submit@bugs.debian.org>; Mon, 10 Jun 2002 14:15:36 +0200
Content-Type: text/plain;
charset="iso-8859-1"
From: Ulrich Eckhardt <uli@doommachine.dyndns.org>
Reply-To: doomster@knuut.de
Subject: bad pathnames coded into the libs
Date: Mon, 10 Jun 2002 14:15:35 +0200
X-Mailer: KMail [version 1.3.2]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
To: submit@bugs.debian.org
Message-Id: <E17HO5A-0002C3-00@monolith.base42.lan>
Delivered-To: submit@bugs.debian.org
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/build/i386-linux/libstdc++-v3/include/bits/char_traits.h
(gdb)
This dir doesn't exist on my machine, and of course I can't step through the
source then.
I must admit that I don't know exactly where the path comes from. I did
cd /usr/lib
grep -r -i home *|grep doko
to find out where the path was hardcoded but to no avail. Maybe it is also my
bad invocation (see bug #149555) that caused the failure.
cheers
Uli
---------------------------------------
Received: (at 149561-close) by bugs.debian.org; 16 Nov 2002 12:54:52 +0000
>From doko@cs.tu-berlin.de Sat Nov 16 06:54:27 2002
Return-path: <doko@cs.tu-berlin.de>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18D2Sm-0002Jf-00; Sat, 16 Nov 2002 06:54:16 -0600
Received: from bolero.cs.tu-berlin.de (daemon@bolero.cs.tu-berlin.de [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id NAA24148
for <149561-close@bugs.debian.org>; Sat, 16 Nov 2002 13:52:00 +0100 (MET)
Resent-From: Matthias Klose <doko@cs.tu-berlin.de>
Received: (from doko@localhost)
by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id gAGCq0N05399;
Sat, 16 Nov 2002 13:52:00 +0100 (MET)
Date: Sat, 16 Nov 2002 13:52:00 +0100 (MET)
Message-Id: <200211161252.gAGCq0N05399@bolero.cs.tu-berlin.de>
Resent-Message-ID: <15830.16240.442086.400612@gargle.gargle.HOWL>
Resent-Date: Sat, 16 Nov 2002 13:52:00 +0100
Resent-To: 149561-close@bugs.debian.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Matthias Klose <doko@cs.tu-berlin.de>
To: 149561-close@bugs.debian-org
Subject: really close #149561
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: 149561-close@bugs.debian.org
X-Spam-Status: No, hits=-4.5 required=5.0
tests=QUOTED_EMAIL_TEXT,RESENT_TO,SPAM_PHRASE_00_01,
SUBJ_HAS_UNIQ_ID
version=2.41
X-Spam-Level:
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 report. adding a paragraph about debugging
libstdc++ for the next upload.
Reply to: