https://sourceware.org/bugzilla/show_bug.cgi?id=30390
--- Comment #5 from Pali Rohár ---
Anyway, I see that for GO32 MZ binaries is bfd using GO32STUB env variable to
specify other custom stub (bfd/coff-stgo32.c). So maybe this can be unified?
--
You are receiving this mail because:
You are on
https://sourceware.org/bugzilla/show_bug.cgi?id=30390
--- Comment #4 from Pali Rohár ---
Ok, I understand reasons. And I think that replacing 64-byte array by another
with same size by some special linker flag has likely very small value, because
this simple replacement can be done by e.g. dd too
https://sourceware.org/bugzilla/show_bug.cgi?id=30390
--- Comment #3 from Nick Clifton ---
Hi Pali,
I must admit that I am reluctant to pursue this feature. This stub is only
used when running an executable in a DOS environment yes ? So its utility in
modern Windows based systems seems to be
https://sourceware.org/bugzilla/show_bug.cgi?id=30390
--- Comment #2 from Pali Rohár ---
Stub is executable code, I think it can be any valid binary in MZ format.
Restrictions about alignement or size would come from the MZ format itself.
About objcopy, I do not know about any way how to replace
https://sourceware.org/bugzilla/show_bug.cgi?id=30390
Nick Clifton changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |nickc at redhat dot com
Last
