Version-Release number of selected component: coreutils-8.21-13.fc19 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: crash_function: set_program_name environ: executable: /usr/bin/yes kernel: 3.14.4-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (1 frames) #2 set_program_name at lib/progname.c:56
Created attachment 907900 [details] File: backtrace
Created attachment 907901 [details] File: cgroup
Created attachment 907902 [details] File: core_backtrace
Created attachment 907903 [details] File: dso_list
Created attachment 907904 [details] File: limits
Created attachment 907905 [details] File: maps
Created attachment 907906 [details] File: open_fds
Created attachment 907907 [details] File: proc_pid_status
Looking at the backtrace: argc=0 , argv[0]=NULL ==> incorrect use of execve or some other function for executing programs (passing null arguments) ==> notabug. I reported this upstream - true and false utilities were fixed ( http://lists.gnu.org/archive/html/bug-coreutils/2009-11/msg00215.html ), behaviour was discussed with glibc maintainers - with resolution that this is execve abusing and not a bug. More details in https://bugzilla.redhat.com/show_bug.cgi?id=498557 and https://bugzilla.redhat.com/show_bug.cgi?id=537684 - true/false fixes were considered exceptions, no other exceptions planned.
Good to know, thanks.