Bug#186020: marked as done (iconv_close gives segmentation fault)
Your message dated Wed, 26 Mar 2003 13:56:21 +0900
with message-id <80u1dqiv4a.wl@oris.opensource.jp>
and subject line Bug#186020: iconv_close gives segmentation fault
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; 23 Mar 2003 22:28:46 +0000
>From oliverh@northwestern.edu Sun Mar 23 16:28:46 2003
Return-path: <oliverh@northwestern.edu>
Received: from merle.it.northwestern.edu [129.105.16.57]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18xDxN-0007PO-00; Sun, 23 Mar 2003 16:28:45 -0600
Received: (from mailnull@localhost)
by merle.it.northwestern.edu (8.12.8/8.12.8) id h2NMSjCh016621
for <submit@bugs.debian.org>; Sun, 23 Mar 2003 16:28:45 -0600 (CST)
Received: from romeo (pistachio-10-186186.nuts.northwestern.edu [129.105.186.186]) by merle.it.northwestern.edu via smap (V2.0)
id xma016524; Sun, 23 Mar 03 16:28:38 -0600
Received: from oliverh by romeo with local (Exim 3.35 #1 (Debian))
id 18xDxE-0000Uw-00
for <submit@bugs.debian.org>; Sun, 23 Mar 2003 16:28:36 -0600
Subject: iconv_close gives segmentation fault
From: "Oliver M. Haynold" <oliverh@northwestern.edu>
To: submit@bugs.debian.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.5
Date: 23 Mar 2003 16:28:36 -0600
Message-Id: <[🔎] 1048458516.1280.8.camel@romeo>
Mime-Version: 1.0
Sender: "Oliver M. Haynold" <oliverh@romeo.it.northwestern.edu>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-0.2 required=4.0
tests=HAS_PACKAGE,SPAM_PHRASE_00_01
version=2.44
X-Spam-Level:
Package: libc6
Version: 2.3.1-15
After updating to libc6 2.3.1-15 some programs (I noticed this behavior
in Evolution 1.0.5 and Gabber 0.8.7-2) give a segmentation fault on
startup. I traced it with gdb and it turned out that the function call
in which the segfault occurs is to iconv_close() in libc6. It works fine
with libc6 2.2.5-11.2.
---------------------------------------
Received: (at 186020-done) by bugs.debian.org; 26 Mar 2003 04:56:24 +0000
>From gotom@debian.or.jp Tue Mar 25 22:56:24 2003
Return-path: <gotom@debian.or.jp>
Received: from oris.opensource.jp (oris.opensource.gr.jp) [218.44.239.73] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18y2xb-0002Io-00; Tue, 25 Mar 2003 22:56:24 -0600
Received: from oris.opensource.jp (oris.opensource.jp [218.44.239.73])
by oris.opensource.gr.jp (Postfix) with ESMTP
id E7C6EC33C6; Wed, 26 Mar 2003 13:56:21 +0900 (JST)
Date: Wed, 26 Mar 2003 13:56:21 +0900
Message-ID: <80u1dqiv4a.wl@oris.opensource.jp>
From: GOTO Masanori <gotom@debian.or.jp>
To: "Oliver M. Haynold" <oliverh@northwestern.edu>
Cc: GOTO Masanori <gotom@debian.or.jp>, 186020-done@bugs.debian.org
Subject: Re: Bug#186020: iconv_close gives segmentation fault
In-Reply-To: <1048653280.5044.108.camel@romeo>
References: <[🔎] 1048458516.1280.8.camel@romeo>
<[🔎] 80n0jljs46.wl@oris.opensource.jp>
<1048646471.1361.103.camel@romeo>
<[🔎] 80y932iwcy.wl@oris.opensource.jp>
<1048653280.5044.108.camel@romeo>
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: 186020-done@bugs.debian.org
X-Spam-Status: No, hits=-2.1 required=4.0
tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,
USER_AGENT
version=2.44
X-Spam-Level:
Hi,
At 25 Mar 2003 22:34:40 -0600,
Oliver M. Haynold <oliverh@northwestern.edu> wrote:
> That's perfectly fine. I don't know what happened and I'm sure that if
> there is a bug it will show up in other systems before libc 2.3 goes
> into stable. Thank you for the time you were taking to try this out,
OK, if you have a time to track this and find the problem in glibc,
please resubmit the bug report. At the present, I close this bug.
Regards,
-- gotom
> On Tue, 2003-03-25 at 22:29, GOTO Masanori wrote:
> > Hmm, but if such major applications got the bug caused from glibc,
> > then we might get a lot of complaints. I think your bug is not
> > glibc's. At least we can't reproduce your bug if you don't do
> > anything... If you're so busy, I close this bug for the present, and
> > wait another report like your problem. Do you think about it?
> >
> > Regards,
> > -- gotom
>
Reply to: