Bug 661981 - [abrt] psmisc-22.13-5.fc14: kill_all: Process /usr/bin/killall was killed by signal 6 (SIGABRT)
Summary: [abrt] psmisc-22.13-5.fc14: kill_all: Process /usr/bin/killall was killed by ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: psmisc
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a3c017114dfb5be81d5fe1dfbc1...
: 671084 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-10 08:55 UTC by leandro
Modified: 2016-02-01 01:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 21:55:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (5.23 KB, text/plain)
2010-12-10 08:55 UTC, leandro
no flags Details

Description leandro 2010-12-10 08:55:47 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: killall gtk-sunlight -o 5s
component: psmisc
crash_function: kill_all
executable: /usr/bin/killall
kernel: 2.6.35.6-48.fc14.i686.PAE
package: psmisc-22.13-5.fc14
rating: 4
reason: Process /usr/bin/killall was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1291971159
uid: 500

How to reproduce
-----
1. i just installed the software (Realtime Sunlight)
2. every time i start up the machine, this error arises
3.

Comment 1 leandro 2010-12-10 08:55:49 UTC
Created attachment 467925 [details]
File: backtrace

Comment 2 Jan Görig 2010-12-10 09:31:13 UTC
Thank you for your bug report. Could you send output of next commands after a crash happens, please? Thanks.

cat /proc/`ps -o pid -C gtk-sunlight h`/stat
uptime

Comment 3 leandro 2010-12-10 09:55:29 UTC
thanks for the help.
here it is the output of your commands, besides i thinks they are not what you expected:


leandro@acero ~$ cat /proc/`ps -o pid -C gtk-sunlight h`/stat
cat: /proc/: Es un directorio
cat: 4581/stat: No existe el fichero o el directorio
leandro@acero ~$ uptime
 10:52:02 up 3 min,  2 users,  load average: 1.81, 1.24, 0.51

i guessed what you were looking for so i did:

leandro@acero ~$ ps -o pid -C gtk-sunlight h
 4581
leandro@acero ~$ cat /proc/4581/stat
4581 (gtk-sunlight) S 4457 4457 4457 0 -1 4202496 2483 23083 0 3 4 1 3 23 20 0 1 0 7676 22257664 2095 4294967295 134512640 134529200 3216916640 3216915984 12497942 0 0 4096 0 3226397190 0 0 17 0 0 0 128 0 0
leandro@acero ~$ uptime
 10:52:57 up 4 min,  2 users,  load average: 1.21, 1.17, 0.53

i hope that were useful for you :)
-Leandro

Comment 4 Jan Görig 2010-12-16 11:11:09 UTC
I can't see any problem there. Could you run and attach output of following test program, please?

http://jgorig.fedorapeople.org/bugzilla/661981/

- Download 'test.c' and compile it with 'gcc test.c -o test'
  Or
  Download binary file for F14 'test'
- run './test < /proc/PID/stat' where PID is number from 'ps -o pid -C gtk-sunlight h
'

Thanks.

Comment 5 leandro 2010-12-16 11:21:11 UTC
leandro@acero leandro$ ./test < /proc/6310/stat
proc_stt_jf: 9861
SC_CLK_TCK: 100.000000
Uptime: 8626.88
Process age: 8528.270000


but surely it looks well, 'cause lately this error already doesnt appear

Comment 6 Jan Görig 2010-12-16 11:37:07 UTC
Numbers are OK. This problem isn't probably in psmisc. There are some issues in killall source but these aren't definitely related with this problem.

If problem occurs again, please reopen this bug and send output of test. Thanks.

Closing.

Comment 7 leandro 2010-12-19 10:45:47 UTC
hi,
im getting again the error.
i paste the trace:

**********************************
[New Thread 2555]
Core was generated by `killall gtk-sunlight -o 5s'.
Program terminated with signal 6, Aborted.
#0  0x0071d416 in __kernel_vsyscall ()

Thread 1 (Thread 2555):
#0  0x0071d416 in __kernel_vsyscall ()
No symbol table info available.
#1  0x0013c531 in raise () from /lib/libc.so.6
No symbol table info available.
#2  0x0013df9e in abort () from /lib/libc.so.6
No symbol table info available.
#3  0x00134e48 in __assert_fail () from /lib/libc.so.6
No symbol table info available.
#4  0x08049ee9 in kill_all (signal=15, names=1, namelist=0xbfad4420, pwent=0x0, scontext=0x0) at killall.c:386
        proc_stt_jf = 10285
        id = <value optimized out>
        found_name = -1
        process_age_sec = -0.84999999999999998
        dir = 0x99d5d00
        de = <value optimized out>
        file = <value optimized out>
        st = {st_dev = 0, __pad1 = 0, __st_ino = 0, st_mode = 0, st_nlink = 0, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 0, st_blksize = 0, st_blocks = 0, st_atim = {tv_sec = 0, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = 0}, st_ctim = {tv_sec = 0, tv_nsec = 0}, st_ino = 0}
        sts = {{st_dev = 0, __pad1 = 0, __st_ino = 0, st_mode = 0, st_nlink = 0, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 0, st_blksize = 0, st_blocks = 0, st_atim = {tv_sec = 0, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = 0}, st_ctim = {tv_sec = 0, tv_nsec = 0}, st_ino = 0} <repeats 32 times>}
        name_len = 0x99d5868
        path = 0x99d5ce8 ""
        comm = "compiz-gtk\000\000s-g"
        command_buf = <value optimized out>
        command = <value optimized out>
        pid_table = <value optimized out>
        pid = -1079168736
        self = 241
        pid_killed = 0x99d5878
        pgids = 0x0
        i = <value optimized out>
        j = <value optimized out>
        okay = <value optimized out>
        length = <value optimized out>
        got_long = <value optimized out>
        error = <value optimized out>
        pids = 242
        max_pids = 0
        pids_killed = <value optimized out>
        found = <value optimized out>
        reglist = 0x0
        lcontext = 0x0
        __PRETTY_FUNCTION__ = "kill_all"
#5  0x0804ae36 in main (argc=4, argv=<value optimized out>) at killall.c:867
        name = <value optimized out>
        sig_num = 15
        optc = <value optimized out>
        myoptind = 3
        pwent = 0x0
        isproc = {st_dev = 3, __pad1 = 0, __st_ino = 19831, st_mode = 33060, st_nlink = 1, st_uid = 500, st_gid = 500, st_rdev = 0, __pad2 = 0, st_size = 0, st_blksize = 1024, st_blocks = 0, st_atim = {tv_sec = 1292755115, tv_nsec = 667119751}, st_mtim = {tv_sec = 1292755115, tv_nsec = 667119751}, st_ctim = {tv_sec = 1292755115, tv_nsec = 667119751}, st_ino = 19831}
        yt = "i\261\004\b\334\327\004\b\300\f*\000\300\f*"
        ot = "5s", '\000' <repeats 13 times>
        options = {{name = 0x804be46 "exact", has_arg = 0, flag = 0x0, val = 101}, {name = 0x804be4c "ignore-case", has_arg = 0, flag = 0x0, val = 73}, {name = 0x804be58 "process-group", has_arg = 0, flag = 0x0, val = 103}, {name = 0x804be66 "younger-than", has_arg = 1, flag = 0x0, val = 121}, {name = 0x804be73 "older-than", has_arg = 1, flag = 0x0, val = 111}, {name = 0x804be7e "interactive", has_arg = 0, flag = 0x0, val = 105}, {name = 0x804be8a "list-signals", has_arg = 0, flag = 0x0, val = 108}, {name = 0x804be97 "quiet", has_arg = 0, flag = 0x0, val = 113}, {name = 0x804be9d "regexp", has_arg = 0, flag = 0x0, val = 114}, {name = 0x804bea4 "signal", has_arg = 1, flag = 0x0, val = 115}, {name = 0x804beab "user", has_arg = 1, flag = 0x0, val = 117}, {name = 0x804beb0 "verbose", has_arg = 0, flag = 0x0, val = 118}, {name = 0x804beb8 "wait", has_arg = 0, flag = 0x0, val = 119}, {name = 0x804bebd "context", has_arg = 1, flag = 0x0, val = 90}, {name = 0x804bec5 "version", has_arg = 0, flag = 0x0, val = 86}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
        scontext = 0x0
        scontext_reg = {buffer = 0xff <Address 0xff out of bounds>, allocated = 4096, used = 0, syntax = 0, fastmap = 0x0, translate = 0xbfad43c0 "", re_nsub = 134533800, can_be_null = 0, regs_allocated = 0, fastmap_accurate = 1, no_sub = 1, not_bol = 1, not_eol = 0, newline_anchor = 0}
From        To          Syms Read   Shared Object Library
0x00953230  0x00964c58  Yes         /lib/libselinux.so.1
0x00126bf0  0x00249104  Yes         /lib/libc.so.6
0x007f6a60  0x007f7a88  Yes         /lib/libdl.so.2
0x005f2850  0x0060ad0f  Yes         /lib/ld-linux.so.2
0x005493b0  0x00549df8  Yes         /usr/lib/gconv/ISO8859-1.so
$1 = 0x99db100 "killall: killall.c:386: kill_all: La declaraci\303\263n `process_age_sec > 0' no se cumple.\n"
No symbol "__glib_assert_msg" in current context.
eax            0x0	0
ecx            0x9fb	2555
edx            0x6	6
ebx            0x9fb	2555
esp            0xbfad228c	0xbfad228c
ebp            0xbfad2298	0xbfad2298
esi            0x25f508	2487560
edi            0x29fff4	2752500
eip            0x71d416	0x71d416 <__kernel_vsyscall+2>
eflags         0x200246	[ PF ZF IF ID ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
Dump of assembler code for function __kernel_vsyscall:
   0x0071d414 <+0>:	int    $0x80
=> 0x0071d416 <+2>:	ret    
End of assembler dump.

**********************************

Comment 8 Jan Görig 2011-01-06 16:23:32 UTC
Thank you for posting backtrace.
process_age_sec is computed from uptime, jiffies and sc_clk_tck. It seems that  problem is caused by wrong uptime value. But I don't know if it is caused by incorrect value in /proc/uptime or by incorrect handling with it.

Could you run my test after this problem occurs again and send its output together with /proc/uptime, please? We are waiting for negative proccess age value. Thanks.

Comment 9 leandro 2011-01-09 07:42:49 UTC
leandro@acero Descargas$ ./test < /proc/6369/stat
proc_stt_jf: 8615
SC_CLK_TCK: 100.000000
Uptime: 250.18
Process age: 164.030000


leandro@acero Descargas$ cat /proc/uptime
284.00 893.68

Comment 10 Jan Görig 2011-01-20 09:27:50 UTC
*** Bug 671084 has been marked as a duplicate of this bug. ***

Comment 11 Fedora Admin XMLRPC Client 2011-05-12 08:55:35 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Jaromír Cápík 2012-01-27 19:40:52 UTC
Hello.

I became a new psmisc maintainer.

Could You please tell me if:
1.) You've already updated to Fedora 15 or higher
2.) the issue is still present

Thanks in advance.

Regards,
Jaromir.

Comment 13 leandro 2012-01-27 21:01:14 UTC
hi!
i haven't updated yet from F14 to F15.
i will report you when i upgrade to F15 if you're still interested.

-Leandro

Comment 14 Fedora End Of Life 2012-08-16 21:56:01 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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