GNOME Bugzilla – Bug 779522
gdb helper code installed as executable scripts but has no #!
Last modified: 2017-03-03 20:09:42 UTC
Created attachment 347124 [details] [review] proposed patch Debian's Lintian tool reports a warning when processing the debug package for GLib: https://lintian.debian.org/tags/executable-not-elf-or-script.html This is because glib_gdb.py and gobject_gdb.py are installed executable, but do not start with "#!" or ELF headers. If a user attempted to run them, the execve() call would fail with ENOEXEC, resulting in either an error or the parent process falling back to using /bin/sh as an interpreter (which would not work, because they are written in Python, not shell). These files are essentially library code, and do not do anything when run, so the solution is to make them not executable. (The same warning is also emitted for echo-script.bat and echo-script in the installed-tests, but I have overridden the warning as a false positive in those cases, because it is deliberate: they are test data for GLib's ability to respond to ENOEXEC by falling back to using /bin/sh as interpreter.)
Review of attachment 347124 [details] [review]: Looks good.
Thanks, fixed in git for 2.51.5 as e3f59e482.