[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#534312: marked as done (upgrade of libc6 causes SEGFAULTs)



Your message dated Wed, 17 Jul 2013 11:56:48 -0700
with message-id <20130717185648.GP14690@google.com>
and subject line Re: upgrade of libc6 causes SEGFAULTs
has caused the Debian Bug report #534312,
regarding upgrade of libc6 causes SEGFAULTs
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
534312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534312
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.9-18
Severity: important

When installing libc6 from unstable on lenny multiple important programs
SEGFAULT. Among them are cups and update-menus.

To reproduce install libc6, libc6-dev, libc6-i386, libc6-dbg and locales 
from sid on lenny and try running update-menus with any parameters.

To examine the problem further I rebuilt update-menus from source with
"-g -O0" and ran it in gdb with the following result:

(gdb) run
Starting program: /home/alve/menu/menu-2.1.41/update-menus/update-menus

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007f9bc7c93149 in *__GI___dl_iterate_phdr (callback=0x7f9bc7ef4d60 <_Unwind_IteratePhdrCallback>, data=0x7fffd08a3370) at dl-iteratephdr.c:75
#2  0x00007f9bc7ef5b59 in _Unwind_Find_FDE (pc=0x7f9bc7ef3f1d, bases=0x7fffd08a3938) at ../../../src/libgcc/../gcc/unwind-dw2-fde-glibc.c:420
#3  0x00007f9bc7ef2f83 in uw_frame_state_for (context=0x7fffd08a3890, fs=<value optimized out>) at ../../../src/libgcc/../gcc/unwind-dw2.c:1121
#4  0x00007f9bc7ef38d9 in uw_init_context_1 (context=0x7fffd08a3890, outer_cfa=0x7fffd08a39d0, outer_ra=0x7f9bc88a6040) at ../../../src/libgcc/../gcc/unwind-dw2.c:1427
#5  0x00007f9bc7ef3f1e in _Unwind_RaiseException (exc=0xa93fd0) at ../../../src/libgcc/../gcc/unwind.inc:93
#6  0x00007f9bc844379d in __cxa_throw () from /usr/lib/libstdc++.so.6
#7  0x0000000000418555 in parsestream::get_char (this=0xa5c670) at parsestream.cc:234
#8  0x0000000000419237 in parsestream::get_name (this=0xa5c670, r=@0x7fffd08a3b70) at parsestream.cc:286
#9  0x000000000040765a in translateinfo (this=0xa5c630, filename=@0x7fffd08a3c40) at update-menus.cc:376
#10 0x0000000000407ce2 in read_roottranslateinfo () at update-menus.cc:997
#11 0x000000000040d1a5 in main (argc=1, argv=0x7fffd08a3f18) at update-menus.cc:1069
(gdb)

When downgrading libc6 and locales to 2.7 and running the same binary again the
problem vanishes.

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6 depends on:
ii  libgcc1                      1:4.3.2-1.1 GCC support library

libc6 recommends no packages.

Versions of packages libc6 suggests:
pn  glibc-doc                     <none>     (no description available)
ii  locales                       2.9-18     GNU C Library: National Language (

-- debconf information:
  glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
* glibc/restart-services: ssh rsync exim4 cups cron atd



--- End Message ---
--- Begin Message ---
Ulf Hermann wrote:

>                                                                     The system
> that originally exhibited the problem has been upgraded to wheezy in the mean
> time, so there is hardly a chance to reproduce the exact setup.

Thanks.  Closing, but if you or anyone else learns more about this, I'd
be happy to revisit it.

--- End Message ---

Reply to: