Hi,
Many thanks for helping me. I inspected the bash command history to
learn what was causing gcc to link 'bogus' executables and found the
cause was -c precisely as you explained. When I removed it a valid
executable was produced that could be run without problems.
Edward
On 10/06/2016, Katola
On Fri, Jun 10, 2016 at 01:42:45PM +0200, Edward Bartolo wrote:
> Hi,
>
> While dissecting the sysvinits (/sbin/init) internals I found that gcc
> can link garbage into an executable file. Attempting to run the
> resultant garbage results in unknown executable format or something
> similar.
>
> I
Hi,
While dissecting the sysvinits (/sbin/init) internals I found that gcc
can link garbage into an executable file. Attempting to run the
resultant garbage results in unknown executable format or something
similar.
I used the -c directive directly on the source code. The command is this:
gcc -a
