Error 4 In Libc-2.13.so
version handling leads to segv on short versions (x.y). Edit Remove 10 This bug affects 1 person Affects Status Importance Assigned to Milestone eglibc (Ubuntu) Edit Confirmed Undecided Unassigned Edit Also affects project (?) Also affects distribution/package Nominate for series Bug Description mantonyan@mantonyan:~$ lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 mantonyan@mantonyan:~$ apt-cache policy libc6 libc6: Installed: 2.13-6ubuntu2 Candidate: 2.13-6ubuntu2 Version table: *** 2.13-6ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status mount.nfs should mount nfs shares both with "sudo mount -t nfs" and with autofs. Neither of the two is operational. One of the recent oneiric updates broke mount.nfs: mantonyan@mantonyan:~$ tail -n 5 /var/log/kern.log Jun 14 15:07:22 localhost kernel: [10960.838858] mount.nfs4[7479]: segfault at 0 ip 00007f499713ea75 sp 00007fff017dfb00 error 4 in libc-2.13.so[7f4997104000+19b000] Jun 14 15:07:32 localhost kernel: [10970.733169] mount.nfs[7486]: segfault at 0 ip 00007fa05f225a75 sp 00007fff074f2080 error 4 in libc-2.13.so[7fa05f1eb000+19b000] Jun 14 15:13:03 localhost kernel: [11301.885900] mount.nfs[7540]: segfault at 0 ip 00007fb3d4eb9a75 sp 00007ffffee1cd20 error 4 in libc-2.13.so[7fb3d4e7f000+19b000] Jun 14 15:13:21 localhost kernel: [11319.915191] mount.nfs[7544]: segfault at 0 ip 00007f72a8716a75 sp 00007fff3ae52c70 error 4 in libc-2.13.so[7f72a86dc000+19b000] Jun 14 15:18:43 localhost kernel: [11642.205869] mount.nfs[7593]: segfault at 0 ip 00007f70f80a8a75 sp 00007fff05459ee0 error 4 in libc-2.13.so[7f70f806e000+19b000] mantonyan@mantonyan:~$ ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libc6 2.13-6ubuntu2 ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2 Uname: Linux 3.0-0-generic x86_64 Architecture: amd64 Date: Tue Jun 14 15:21:14 2011 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: eglibc UpgradeStatus: Upgraded to oneiric on 2009-03-03 (833 days ago) Tags: amd64 apport-bug apport-lpi oneiric unity-2d Edit Tag help Merelin (merelin) wrote on 2011-06-14: #1 Dependencies.txt Edit (418 bytes, text/plain; charset="utf-8") Jean-Baptiste Lallement (jibel) wrote on 2011-06-14: #2 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 796611, so it is being
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Configure kern.log to give more info https://bugs.launchpad.net/bugs/797157 about a segfault up vote 0 down vote favorite Currently I can find in kern.log entries like this: [6516247.445846] ex3.x[30901]: segfault at 0 ip 0000000000400564 sp 00007fff96ecb170 error 6 in ex3.x[400000+1000] [6516254.095173] ex3.x[30907]: segfault at 0 ip 0000000000400564 sp 00007fff0001dcf0 error 6 in ex3.x[400000+1000] [6516662.523395] ex3.x[31524]: segfault at 7fff80000000 ip 00007f2e11e4aa79 sp 00007fff807061a0 error 4 in libc-2.13.so[7f2e11dcf000+180000] (You see, apps causing segfault are named ex3.x, means http://stackoverflow.com/questions/25714501/configure-kern-log-to-give-more-info-about-a-segfault exercise 3 executable). Is there a way to ask kern.log to log the complete path? Something like: [6...] /home/user/cclass/ex3.x[3...]: segfault at 0 ip 0564 sp 07f70 error 6 in ex3.x[4...] So I can easily figure out from who (user/student) this ex3.x is? Thanks! Beco linux logging segmentation-fault kernel debian share|improve this question asked Sep 7 '14 at 20:32 Dr Beco 3,15122343 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote accepted +50 The short answer is: No, it is not possible without making code changes and recompiling the kernel. The normal solution to this problem is to instruct your students to name their executable
Sign in Pricing Blog Support Search GitHub This repository Watch 76 Star https://github.com/dlundquist/sniproxy/issues/86 760 Fork 158 dlundquist/sniproxy Code Issues 29 Pull requests 3 Projects 0 Wiki Pulse Graphs New issue Sniproxy segfaults #86 Closed nielspeen opened this Issue Apr 17, 2014 · 5 comments Projects None yet Labels Bug Needs Info Milestone No milestone Assignees No one assigned error 4 2 participants nielspeen commented Apr 17, 2014 I've installed sniproxy on some busier servers and on all of them SNIPROXY segfaults regularly. What's the best way to provide you with useful feedback? [1423254.751712] sniproxy[7827]: segfault at 1000 ip 00007fbbeed70cba sp 00007fff7179ecc0 error 4 in libc-2.13.so[7fbbeed2b000+182000] [1423281.360516] sniproxy[7864]: segfault error 4 in at 1000 ip 00007f7f64763cba sp 00007fff39c5a9c0 error 4 in libc-2.13.so[7f7f6471e000+182000] [1423335.440955] sniproxy[7915]: segfault at 1000 ip 00007fba681cccba sp 00007fffaf704080 error 4 in libc-2.13.so[7fba68187000+182000] [1423343.364001] sniproxy[7944]: segfault at 1000 ip 00007f8f07552cba sp 00007fff4a5c4ba0 error 4 in libc-2.13.so[7f8f0750d000+182000] [1423373.626337] sniproxy[7951]: segfault at 1000 ip 00007f1e0fa61cba sp 00007fff51cc8470 error 4 in libc-2.13.so[7f1e0fa1c000+182000] [1423403.690315] sniproxy[7987]: segfault at 1000 ip 00007f0fcf948cba sp 00007fff97e78920 error 4 in libc-2.13.so[7f0fcf903000+182000] [1423433.361416] sniproxy[7996]: segfault at 1000 ip 00007f2424c75cba sp 00007ffffc6f79e0 error 4 in libc-2.13.so[7f2424c30000+182000] [1424199.700092] sniproxy[8028]: segfault at 1000 ip 00007f0602d6ecba sp 00007fffe381d150 error 4 in libc-2.13.so[7f0602d29000+182000] [1424225.997099] sniproxy[8394]: segfault at 1000 ip 00007f489fe0bcba sp 00007fff0f35cbd0 error 4 in libc-2.13.so[7f489fdc6000+182000] Owner dlundquist commented Apr 17, 2014 @nielspeen A core dump and/or backtrace would be helpful to identify where this is occurring, along with the revision of sniproxy you are running. To obtain a backtrace: Compile sniproxy with debugging symbols ./configure CC=