Created attachment 1114950 [details]
File: backtrace

Created attachment 1114951 [details]
File: cgroup

Created attachment 1114952 [details]
File: core_backtrace

Created attachment 1114953 [details]
File: dso_list

Created attachment 1114954 [details]
File: limits

Created attachment 1114955 [details]
File: maps

Created attachment 1114956 [details]
File: mountinfo

Created attachment 1114957 [details]
File: namespaces

Created attachment 1114958 [details]
File: open_fds

Created attachment 1114959 [details]
File: proc_pid_status

Created attachment 1114960 [details]
File: var_log_messages

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.

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