Re: [RFA] new test for separate debug info

[Elena Zannoni <ezannoni at redhat dot com>]

Michael Elizabeth Chastain writes:
 > Elena Zannoni writes:
 > 
 >     # If we have too many warnings or errors,
 >     # the output of the test can't be considered correct.
 >     if { $warning_threshold > 0 && $warncnt >= $warning_threshold
 > 	 || $perror_threshold > 0 && $errcnt >= $perror_threshold } {
 >         verbose "Error/Warning threshold exceeded: \
 >                  $errcnt $warncnt (max. $perror_threshold $warning_threshold)"
 >         set type UNRESOLVED
 >     }
 > 
 > Ick!
 > 
 > > what to do? Maybe just get rid of the unsupported call, and just get
 > > out of the test.
 > 
 > Well, "nothing different" is okay.  I'm not worried about the actual
 > output, as long as we understand why it behaves that way, and stick that
 > understanding into a comment somewhere.
 > 
 > As Daniel alluded to -- what SHOULD happen when an end user tries
 > to do this with stabs+?  Should binutils bonk out with a nice error
 > message?
 > 

I think binutils is a bit confused with separate debug info and stabs.
That would need to be fixed as well. I am really tempted to just bail
out for stabs.

elena


 > Michael C