Bug#186020: iconv_close gives segmentation fault
At 25 Mar 2003 20:41:11 -0600,
Oliver M. Haynold <email@example.com> wrote:
> Unfortunately, I forgot to save the backtrace before I downgraded (a bit
> panicked) back to 2.2.5-11.2, so I don't have anything to give you right
> now. If you have time to investigate the problem maybe you'll be able to
> reproduce it if you put the Gabber 0.8.7-2 package on a 2.3.1 system.
I installed gabber (0.8.7.cvs20020712-6 in sid), and it works well
under LANG=ja_JP.eucJP locale with glibc 2.3.1-16. When does the
> I'm sorry that I can't be of much help now and I certainly don't have
> any expectations that you do something about the problem, but I wanted
> to have reported it because it did appear in two different applications
> and was cured by downgrading libc6.
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?
> On Sun, 2003-03-23 at 22:39, GOTO Masanori wrote:
> > At 23 Mar 2003 16:28:36 -0600,
> > Oliver M. Haynold <firstname.lastname@example.org> wrote:
> > > 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.
> > Could you provide the example source code, or back trace? In
> > addition, at least my iconv test program does not crash, so it's your
> > environment problem, or caller program problem, or environment
> > dependent problem.