[binutils-gdb] Fix failed exec error message

[sergiodj+buildbot at redhat dot com]

*** TEST RESULTS FOR COMMIT fe23c31f262151ce3265f5b90870d40cb6840f0a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: fe23c31f262151ce3265f5b90870d40cb6840f0a

Fix failed exec error message
Ref: https://sourceware.org/ml/gdb-patches/2015-07/msg00629.html

This fixes the bogus command line in the error message shown when the
SHELL environment variable points somewhere that's not something that
resembles a shell:

  $ SHELL=/nonexisting gdb /home/pedro/a.out
  (gdb) r
  Starting program: /home/pedro/a.out
 - Cannot exec /home/pedro/a.out -c exec /home/pedro/a.out .
 + Cannot exec /nonexisting -c exec /home/pedro/a.out .
  Error: No such file or directory
  During startup program exited with code 127.
  (gdb)

gdb/ChangeLog:
2015-07-24  Pedro Alves  <palves@redhat.com>

	* fork-child.c (fork_inferior): Print argv[0] instead of exec_file.