Re: [PATCH] set osabi command

[Andrew Cagney <ac131313@ges.redhat.com>]

> On Mon, Aug 19, 2002 at 06:31:54PM -0400, Andrew Cagney wrote:
> 
>  > It gets complex though because the user could enter a sequence like:
>  > 
>  > (gdb) set architecture arm
>  > ... architecture forced to arm ...
>  > (gdb) set osabi arm_eabi_v1
>  > ... osabi forced to arm_eabi_v1
>  > (gdb) set architecture mips
>  > ... architecture forced to mips, what should happen to the OSABI?  It 
>  > can't remain arm_eabi_v1 ...
>  > 
>  > Idea's?
> 
> 	* If it's e.g. "NetBSD/ELF", it's perfectly valid for ARM and MIPS,
> 	  so it should stay the same.
> 
> 	* Failing that, if the target triplet has a default OSABI, then
> 	  that should be selected.
> 
> 	* Failing that, the "unknown" OSABI.

Are you suggesting that a ``set architecture'' command affect the ``set 
osabi'' setting, possibly forcing it to some other value?

Another option is:

	...
	(gdb) set architecture mips
	OSABI arm_eabi_v1 invalid for mips architecture

and possibly even:

	Force OSABI to ``auto''?  (y or n)

even figuring out that there is a clash is hairy.

enjoy,
Andrew