Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 52124 - lastlog gives a seg fault on AMD 64
Summary: lastlog gives a seg fault on AMD 64
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
: 52123 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-05-26 12:10 UTC by Jacob Martin
Modified: 2004-06-07 01:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Martin 2004-05-26 12:10:04 UTC
I couldn't find the AMD 64 category, but I have a fresh build of shadow and if I run 

/usr/bin/lastlog

Username         Port     From             Latest
Segmentation fault


There is no core file.  What should I do, recompile with debug on and try again?  Maybe I have a corrupt wtmp file?
Comment 1 Jacob Martin 2004-05-26 12:20:06 UTC
*** Bug 52123 has been marked as a duplicate of this bug. ***
Comment 2 Jason Huebel (RETIRED) gentoo-dev 2004-05-27 07:00:06 UTC
Please provide your "emerge info", as well as recompiling lastlog with debugging on.  Provide a backtrace of lastlog.
Comment 3 Jacob Martin 2004-05-27 10:41:11 UTC
I'm a new Gentoo user, so unfortunately, I'm not quite sure how to turn on debugging in the compiler.  I tried setting DEBUGBUILD="true" in /etc/make.conf, but that didn't seem to work.  Please advise how to accomplish this.

Below is my emerge information
===============================
mygentoo root # emerge info
Portage 2.0.50-r6 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.2-r9, 2.6.5-gentoo)
=================================================================
System uname: 2.6.5-gentoo x86_64 4
Gentoo Base System version 1.4.10
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2 -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox sfperms userpriv usersandbox"
GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa amd64 apm arts avi berkdb cdr crypt encode esd foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 imlib jpeg kde ldap libg++ libwww mikmod motif mozilla mpeg mysql ncurses nls nogcj oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline sdl slang spell ssl tcltk tcpd tetex truetype xml2 xmms xv zlib"

Comment 4 Jason Huebel (RETIRED) gentoo-dev 2004-05-27 14:14:45 UTC
USE="debug" FEATURES="nostrip" emerge shadow

Then get a backtrace by running: gdb lastlog

At the gdb prompt, type "run". It should then segfault as you mentioned.  Then type "bt" (for backtrace) to get the backtrace information.  Add that information as a comment to this bug report.
Comment 5 Jacob Martin 2004-05-27 14:32:51 UTC
Thanks for the info.  I did it, but it says that there is still some debugging info missing.  Let me know if this trace isn't enough and what to re-compile with debug to give you more info.

(gdb) run
Starting program: /usr/bin/lastlog
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...Username         Port     From             Latest

Program received signal SIGSEGV, Segmentation fault.
0x0000002a95943db7 in strftime () from /lib/libc.so.6
(gdb) bt
#0  0x0000002a95943db7 in strftime () from /lib/libc.so.6
#1  0x000000000040108f in ?? ()
#2  0x000000000040103c in ?? ()
#3  0x0000000000400efb in ?? ()
#4  0x0000002a958c78b1 in __libc_start_main () from /lib/libc.so.6
#5  0x0000000000400caa in ?? ()
(gdb)

Comment 6 Travis Tilley (RETIRED) gentoo-dev 2004-06-05 12:27:52 UTC
i cant reproduce this bug here, with glibc 2.3.4.20040605
Comment 7 Jacob Martin 2004-06-05 15:45:08 UTC
Aha!  I have glibc version 2.3.2-r9

I'll update the bug once I can get the new glibc successfully emerged to 2.3.3_pre20040529
Comment 8 Jacob Martin 2004-06-06 18:16:35 UTC
Ok, I still get it on 2.3.3_pre20040529 AND 2.3.4.20040605!

The backtrace with the current version is identical in every version!!
Comment 9 Jacob Martin 2004-06-07 01:01:10 UTC
Ok, just did a fresh emerge of a few packages, and it no longer is happening.