Re: [rfc] [7/9] Multi-target support: Fix GDB_OSABI_OPENBSD_AOUT problem

["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 m88k, we don't support NetBSD at all, so this is no problem.

On m68k, we support both NetBSD and OpenBSD, but they use the
same gdbarch structure (with no OSABI handlers at all), so this
is no problem (currently) either.

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?

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.

Otherwise, the suggestion implemented in my patch would be to at
least offer two separate OSABI settings for the two operating
systems; this will at least enable users to manually select the
correct OS, if it cannot be detected automatically ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com