On Sat, Apr 08, 2017 at 01:28:34AM +, David Holland wrote:
> On Fri, Apr 07, 2017 at 07:17:05PM +0200, Kamil Rytarowski wrote:
> > What's the purpose of ELFOSABI_NETBSD on NetBSD?
>
> Short answer: the OSABI field in the elf header was added way too late
> for it
On Fri, Apr 07, 2017 at 07:17:05PM +0200, Kamil Rytarowski wrote:
> What's the purpose of ELFOSABI_NETBSD on NetBSD?
Short answer: the OSABI field in the elf header was added way too late
for it to be widely adopted or honored. :-/
--
David A. Holland
dholl...@netbsd.org
On 07.04.2017 23:10, Christos Zoulas wrote:
> On Apr 7, 7:17pm, n...@gmx.com (Kamil Rytarowski) wrote:
> -- Subject: ELFOSABI_NETBSD
>
> | Currently we set e_ident[EI_OSABI] to ELFOSABI_SYSV. This makes parsing
> | NetBSD core(5) core files cross-system little bit less obvious.
On Apr 7, 7:17pm, n...@gmx.com (Kamil Rytarowski) wrote:
-- Subject: ELFOSABI_NETBSD
| Currently we set e_ident[EI_OSABI] to ELFOSABI_SYSV. This makes parsing
| NetBSD core(5) core files cross-system little bit less obvious. In LLDB
| we are recognized as generic or unknown unix.
|
| Function
What's the purpose of ELFOSABI_NETBSD on NetBSD?
Currently we set e_ident[EI_OSABI] to ELFOSABI_SYSV. This makes parsing
NetBSD core(5) core files cross-system little bit less obvious. In LLDB
we are recognized as generic or unknown unix.
Function ELFNAMEEND(coredump):
161 /