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

Bug#679172: marked as done (libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so)

Your message dated Fri, 29 Jun 2012 23:09:51 -0500
with message-id <20120630040906.GA3486@burratino>
and subject line [axst@users.sourceforge.net: Re: ls[8213]: segfault in libc-2.11.3.so]
has caused the Debian Bug report #679172,
regarding libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so
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.)


-- 
679172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679172
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-i686
Version: 2.11.3-3
Severity: normal
File: libc-2.11.3.so


Just found this in /var/log/kern.log and /var/log/messages:

ls[8213]: segfault at 1ebbc787 ip b769aa53 sp bffcbc14 error 4 in libc-2.11.3.so[b7626000+140000]

ls seemed to work normally, though.

-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6-i686 depends on:
ii  libc6                         2.11.3-3   Embedded GNU C Library: Shared lib

libc6-i686 recommends no packages.

libc6-i686 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Forwarding with permission.
--- Begin Message --- 
Hi, Jonathan,

I see what you mean. Looking at /var/log/kern.log again, I have just noticed something a
bit strange:

Jun 26 17:32:24 tulip kernel: [38097.453497] sshd[5014]: segfault at cebc3057 ip b7354a53 sp bfa6f364 error 5 in libc-2.11.3.so[b72e0000+140000]
Jun 26 17:32:26 tulip kernel: [38098.938167] sshd[5025]: segfault at ce7e33cf ip b734ea53 sp bfaccb34 error 5 in libc-2.11.3.so[b72da000+140000]
Jun 26 17:32:53 tulip kernel: [38126.483606] grep[5069]: segfault at 201f513b ip b76e0a53 sp bfaa7b34 error 4 in libc-2.11.3.so[b766c000+140000]
Jun 26 17:33:14 tulip kernel: [38147.117780] grep[5108]: segfault at 2041258b ip b76a1a53 sp bfdce394 error 4 in libc-2.11.3.so[b762d000+140000]
Jun 26 17:33:16 tulip kernel: [38148.904277] ls[5111]: segfault at 1fe9b770 ip b766da53 sp bf8413a4 error 4 in libc-2.11.3.so[b75f9000+140000]
Jun 26 22:03:10 tulip kernel: [54343.297123] ls[8213]: segfault at 1ebbc787 ip b769aa53 sp bffcbc14 error 4 in libc-2.11.3.so[b7626000+140000]

It never happened before, and the messages preceding (Jun 26 17:23:01 tulip kernel:
[37534.196807]) and following (Jun 27 17:24:23 tulip kernel: [124015.641028]) the ones
quoted here concern totally different things.

And, of course, I cannot reproduce the problem. Sorry. I hope it is not a serious hardware
problem.

Very curious and a bit worried myself,

Axel

--- End Message ---

--- End Message ---
Reply to: