Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#679172: libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so

416 views
Skip to first unread message

ax...@users.sourceforge.net

unread,
Jun 26, 2012, 4:50:02 PM6/26/12
to
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



--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Jonathan Nieder

unread,
Jun 26, 2012, 5:00:02 PM6/26/12
to
Hi Axel,

ax...@users.sourceforge.net wrote:

> 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]

If anything, this would be a symptom of memory corruption or a bug in
"ls". Can you reproduce it?

Curious,
Jonathan

Aurelien Jarno

unread,
Jun 29, 2012, 7:30:02 PM6/29/12
to
tag 679172 + moreinfo
thanks

On Tue, Jun 26, 2012 at 10:31:46PM +0200, ax...@users.sourceforge.net wrote:
> 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.
>

Most of this kind of reports are actually not libc fault, but program
passing wrong arguments to some libc functions (like NULL to strlen()).

Please provide a way to reproduce the issue.

--
Aurelien Jarno GPG: 1024D/F1BCDB73
aure...@aurel32.net http://www.aurel32.net

ax...@users.sourceforge.net

unread,
Jul 13, 2012, 3:00:02 AM7/13/12
to
Sorry, it was a severe hardware problem on the main board, probably the CPU − I could not
even boot up the system again once after shutting it down. This just goes to show how
robust Linux is because it just reported a few segfaults from time to time.

Axel
0 new messages