Bug 1298736

Summary: [abrt] coreutils: set_program_name(): cat killed by SIGABRT
Product: [Fedora] Fedora Reporter: Richard Geary <tristram987>
Component: coreutilsAssignee: Ondrej Vasik <ovasik>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: admiller, fedora, kdudka, kzak, ooprala, ovasik, p, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f546d898ca8b62e2fd8de80fe2606c8d9e383567
Whiteboard: abrt_hash:f21649dbc5694b13a490f417199c07040e564d0d;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-15 17:52:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Richard Geary 2016-01-14 21:04:13 UTC 
Description of problem:
Running JetBrains CLion, I ran a gtest application which succeeded

Version-Release number of selected component:
coreutils-8.24-4.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        
crash_function: set_program_name
environ:        
executable:     /usr/bin/cat
global_pid:     26515
kernel:         4.2.8-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #2 set_program_name at lib/progname.c:56

Potential duplicate: bug 1108414
Comment 1 Richard Geary 2016-01-14 21:04:20 UTC 
Created attachment 1114950 [details]
File: backtrace
Comment 2 Richard Geary 2016-01-14 21:04:21 UTC 
Created attachment 1114951 [details]
File: cgroup
Comment 3 Richard Geary 2016-01-14 21:04:22 UTC 
Created attachment 1114952 [details]
File: core_backtrace
Comment 4 Richard Geary 2016-01-14 21:04:24 UTC 
Created attachment 1114953 [details]
File: dso_list
Comment 5 Richard Geary 2016-01-14 21:04:25 UTC 
Created attachment 1114954 [details]
File: limits
Comment 6 Richard Geary 2016-01-14 21:04:26 UTC 
Created attachment 1114955 [details]
File: maps
Comment 7 Richard Geary 2016-01-14 21:04:27 UTC 
Created attachment 1114956 [details]
File: mountinfo
Comment 8 Richard Geary 2016-01-14 21:04:28 UTC 
Created attachment 1114957 [details]
File: namespaces
Comment 9 Richard Geary 2016-01-14 21:04:29 UTC 
Created attachment 1114958 [details]
File: open_fds
Comment 10 Richard Geary 2016-01-14 21:04:31 UTC 
Created attachment 1114959 [details]
File: proc_pid_status
Comment 11 Richard Geary 2016-01-14 21:04:32 UTC 
Created attachment 1114960 [details]
File: var_log_messages
Comment 12 Ondrej Vasik 2016-01-15 17:52:21 UTC 
This is not a bug.

Snippet from the code (lib/progname.c):
if (argv0 == NULL)
    {
      /* It's a bug in the invoking program.  Help diagnosing it.  */
      fputs ("A NULL argv[0] was passed through an exec system call.\n",
             stderr);
      abort ();
    }


In other words, if you run exec which calls the program, but with argv[0] NULL, program aborts and - and this is expected behaviour chosen by upstream.
Comment 13 sedrubal 2016-01-18 00:44:26 UTC 
Another user experienced a similar problem:

I started ls with an empty argv...

char *args[] = { NULL };
execvp("ls", args);

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        
crash_function: set_program_name
environ:        
executable:     /usr/bin/ls
global_pid:     10997
kernel:         4.3.3-300.fc23.x86_64
package:        coreutils-8.24-5.fc23
reason:         ls killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000