Re: [patch/rfc] Don't complain about unknown OSABI

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

> On Sun, Aug 18, 2002 at 11:41:01AM -0400, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> The attached patch removes the warning message that is printed when the 
>> OSABI is unknown (all the sniffers failed).
>> 
>> When debugging an embedded executable, there is no OSABI info.  Hence I 
>> don't think the warning should be issued.  This can be seen when 
>> debugging a GCC created, mips-elf executable.
>> 
>> thoughts?
>> Andrew
> 
> 
> I like it.  I asked for this change about two months ago when I noticed
> it on mips-elf.  And there's a typo in the message you're removing,
> too.

> [On the related hand, we just had some reports about a case where the OS
> ABI is isn't detected (on uClibc) - do you think a (configure.tgt based
> or *.mt based rather than in a header, I think) way to specify the
> default OS ABI based on the target triplet would be appropriate?

I know.  Being able to print the OSABI would help (set/show abi).

I think it should ask BFD.  BFD can then go and look at the target 
tuple. That would mean that BFD and GDB are ``on the same page''.   See 
the hacks I've got GDB pulling to figure out the default architecture.

> Linux kernels do not have ABI tagging, which comes from glibc, but
> generally use the Linux OS ABI.]

Andrew