RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 831245 - dump-utmp Segmentation fault on ppc64
Summary: dump-utmp Segmentation fault on ppc64
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: psacct
Version: 6.2
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jaromír Cápík
QA Contact: Branislav Náter
URL:
Whiteboard:
Depends On:
Blocks: 834216 834217 836160 869966
TreeView+ depends on / blocked
 
Reported: 2012-06-12 14:44 UTC by Branislav Náter
Modified: 2016-02-01 01:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 869966 (view as bug list)
Environment:
Last Closed: 2013-11-14 10:37:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
strace output of dump-utmp (2.28 KB, text/plain)
2012-06-12 14:44 UTC, Branislav Náter
no flags Details

Description Branislav Náter 2012-06-12 14:44:44 UTC
Created attachment 591215 [details]
strace output of dump-utmp

Description of problem:
dump-utmp recieved SIGSEGV when trying to process /var/log/wtmp file.

Version-Release number of selected component (if applicable):
psacct-6.3.2-63.el6.ppc64

How reproducible:
always on ppc64

Steps to Reproduce:
1. run dump-utmp /var/log/wtmp 
  
Actual results:
Segmentation fault

Expected results:
correct output

Additional info:
gdb output:
# gdb dump-utmp
<snip>
Reading symbols from /usr/sbin/dump-utmp...Reading symbols from /usr/lib/debug/usr/sbin/dump-utmp.debug...done.
done.
(gdb) run /var/log/wtmp
Starting program: /usr/sbin/dump-utmp /var/log/wtmp

Program received signal SIGSEGV, Segmentation fault.
0x000000809e259834 in .strlen () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.25.el6_1.3.ppc64
(gdb) t a a bt

Thread 1 (process 1159):
#0  0x000000809e259834 in .strlen () from /lib64/libc.so.6
#1  0x000000809e23b2b8 in ._IO_fputs () from /lib64/libc.so.6
#2  0x0000000010001cf8 in print_utmp_record (rec=0x10020070, out=0x809e3706a0) at utmp_rd.c:121
#3  0x0000000010001000 in main (argc=<value optimized out>, argv=0xffffffff188) at dump-utmp.c:113

Comment 1 Jaromír Cápík 2012-06-20 16:27:59 UTC
I've already fixed the issue. Other architectures are affected too (no crash, but incorrect timestamps).


Note You need to log in before you can comment on or make changes to this bug.