Your message dated Fri, 24 Sep 2004 11:54:18 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#272654: update from 2.2.5-11.2 to 2.3.2.ds1-16 breaks
statically-linked program
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; 21 Sep 2004 09:53:31 +0000
>From [EMAIL PROTECTED] Tue Sep 21 02:53:31 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mailout09.sul.t-online.com [194.25.134.84]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C9hL1-0003G0-00; Tue, 21 Sep 2004 02:53:31 -0700
Received: from fwd06.aul.t-online.de
by mailout09.sul.t-online.com with smtp
id 1C9hKx-00024u-01; Tue, 21 Sep 2004 11:53:27 +0200
Received: from wanza.invalid ([EMAIL PROTECTED]) by fwd06.sul.t-online.com
with esmtp id 1C9hKp-097ueO0; Tue, 21 Sep 2004 11:53:19 +0200
Received: from martin by wanza.invalid with local (Exim 3.35 #1 (Debian))
id 1C9hHj-000385-00; Tue, 21 Sep 2004 11:50:07 +0200
From: [EMAIL PROTECTED] (Martin Lottermoser)
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: update from 2.2.5-11.2 to 2.3.2.ds1-16 breaks statically-linked program
X-Mailer: reportbug 1.50
Date: Tue, 21 Sep 2004 11:50:02 +0200
Message-Id: <[EMAIL PROTECTED]>
X-ID: TvZvWvZSYelLDVzLCS7TrtMMkUhezkTjy5Xaxl-8fBspz5jJyPVnkq
X-TOI-MSGID: 153d2697-6207-4b88-8bd8-4707c69b02b6
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.5 required=4.0 tests=BAYES_10,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: libc6
Version: 2.3.2.ds1-16
Severity: normal
Hello,
I'm running a Debian 3.0 r1 system and wanted to upgrade libc6 from
2.2.5-11.2 to the version in "testing" (2.3.2.ds1-16). This seemed
to work fine, but then a statically-linked program which is part of
my backup pipeline dumped core. (Source code, binary, and core file
are available on request.)
Gdb shows the following stack trace:
#0 0x00000000 in ?? ()
#1 0x40167345 in ?? ()
#2 0x40130788 in ?? ()
#3 0x4010f298 in ?? ()
#4 0x4000d38c in ?? ()
#5 0x4000ef09 in ?? ()
#6 0x08058239 in getpwuid_r ()
#7 0x08057f5f in getpwuid ()
#8 0x08048699 in schreibe_tar_Praefix (aus=3, Blockgroesse=10240, Daten=0xbffffa40)
at blocke.c:265
#9 0x08049a2c in main (argc=4, argv=0xbffffac4) at blocke.c:793
I recovered /lib from a previous backup into a separate directory
and called the program with LD_LIBRARY_PATH set to this new
directory: it worked as expected. Linking dynamically also produced
a working program.
I have since downgraded to the older libc6 version and the problem
is gone. (Incidentally, downgrading did not happen without problems:
a broken pipe in a command called by apt-get prevented execution.
Deleting the entries for /lib/libdb* from libdb1-compat.list led to
success.)
Before downgrading, I saved the /lib hierarchy. After the downgrade
I ran my program with LD_LIBRARY_PATH set to this directory: the core
happens.
Although I no longer personally have a problem, I thought I'ld better
report this in case other people run into it, too. Also, I'ld *really*
like to understand how installing a new libc6 package can affect a
program without dynamic dependencies :-).
Yours sincerely,
Martin Lottermoser
--
Martin Lottermoser [EMAIL PROTECTED]
Greifswaldstrasse 28
38124 Braunschweig Telephone: +49 (531) 6802747
Germany
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux wanza 2.4.23 #30 Mon Jul 5 18:58:11 CEST 2004 i686
Locale: LANG=de_DE, LC_CTYPE=de_DE
---------------------------------------
Received: (at 272654-done) by bugs.debian.org; 24 Sep 2004 02:54:19 +0000
>From [EMAIL PROTECTED] Thu Sep 23 19:54:19 2004
Return-path: <[EMAIL PROTECTED]>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CAgDz-0004Xa-00; Thu, 23 Sep 2004 19:54:19 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
by webmasters.gr.jp (Postfix) with ESMTP
id ABDF4DEB80; Fri, 24 Sep 2004 11:54:18 +0900 (JST)
Date: Fri, 24 Sep 2004 11:54:18 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] (Martin Lottermoser),
[EMAIL PROTECTED]
Subject: Re: Bug#272654: update from 2.2.5-11.2 to 2.3.2.ds1-16 breaks
statically-linked program
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
(i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
At Tue, 21 Sep 2004 11:50:02 +0200,
Martin Lottermoser wrote:
> I'm running a Debian 3.0 r1 system and wanted to upgrade libc6 from
> 2.2.5-11.2 to the version in "testing" (2.3.2.ds1-16). This seemed
> to work fine, but then a statically-linked program which is part of
> my backup pipeline dumped core. (Source code, binary, and core file
> are available on request.)
You may be surprised that glibc cares about static linked program
minimally (think about dlopen and NSS plugins).
> Gdb shows the following stack trace:
>
> #0 0x00000000 in ?? ()
> #1 0x40167345 in ?? ()
> #2 0x40130788 in ?? ()
> #3 0x4010f298 in ?? ()
> #4 0x4000d38c in ?? ()
> #5 0x4000ef09 in ?? ()
> #6 0x08058239 in getpwuid_r ()
> #7 0x08057f5f in getpwuid ()
> #8 0x08048699 in schreibe_tar_Praefix (aus=3, Blockgroesse=10240,
> Daten=0xbffffa40) at blocke.c:265
> #9 0x08049a2c in main (argc=4, argv=0xbffffac4) at blocke.c:793
I guess it's NSS issue. getpwuid() touches NSS (Name Service Switch)
code. It opens /lib/libnss*.so via dlopen() from the static linked
glibc. Look at this example:
[EMAIL PROTECTED]:~/debian/glibc/bugs/272654> cat test.c
#include <pwd.h>
#include <sys/types.h>
int main(void)
{
struct passwd *p = getpwuid(0);
return 0;
}
[EMAIL PROTECTED]:~/debian/glibc/bugs/272654> gcc test.c -static
/tmp/cciqrtaW.o(.text+0x18): In function `main':
: warning: Using 'getpwuid' in statically linked applications requires at
runtime the shared libraries from the glibc version used for linking
Unfortunatelly we can't fix this problem. I closed this bug.
Regards,
-- gotom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
