This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] [7/9] Multi-target support: Fix GDB_OSABI_OPENBSD_AOUT problem
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: uweigand at de dot ibm dot com
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 29 Oct 2007 21:31:48 +0100 (CET)
- Subject: Re: [rfc] [7/9] Multi-target support: Fix GDB_OSABI_OPENBSD_AOUT problem
- References: <200710292019.l9TKJ78e001372@d12av02.megacenter.de.ibm.com>
> Date: Mon, 29 Oct 2007 21:19:07 +0100 (CET)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
>
> Mark Kettenis wrote:
>
> > The last OpenBSD/i386 release that used a.out was OpenBSD 3.3, which
> > was released more than four years ago. I have no problem with
> > dropping a.out support for OpenBSD/i386 if that makes things easier.
> >
> > However, OpenBSD/vax, OpenBSD/m68k and OpenBSD/m88k are still a.out,
> > so parts of your diff might still be required (didn't look at the
> > details of your diff yet).
>
> The problem occurs whenever we want to support both OpenBSD-a.out
> and NetBSD-a.out on the same platform, and they both want to install
> (different) OSABI handlers.
>
> On vax, both NetBSD and OpenBSD want to install an OSABI handler,
> so this *is* a problem. However, the NetBSD OSABI handler doesn't
> actually do anything -- do you know the status of NetBSD/vax?
NetBSD/vax has been using ELF since NetBSD 1.5 or 1.6. I guess this
means NetBSD/vax a.out could be dropped.
> If we can resolve the vax question, and indeed drop a.out support
> for either NetBSD/i386 or OpenBSD/i386, this would solve the problem
> as well.
Probably both can be dropped. NetBSD/i386 started using ELF before
OpenBSD/i386, but I have no problem with dropping OpenBSD/i386 a.out
support.
Mark