From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22572 invoked by alias); 14 Nov 2003 19:37:26 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22552 invoked from network); 14 Nov 2003 19:37:25 -0000 Received: from unknown (HELO granger.mail.mindspring.net) (207.69.200.148) by sources.redhat.com with SMTP; 14 Nov 2003 19:37:25 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AKjky-0006q1-00; Fri, 14 Nov 2003 14:37:24 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 872554B3FA; Fri, 14 Nov 2003 14:37:14 -0500 (EST) To: ezannoni@redhat.com Subject: Re: [RFA] new test for separate debug info Cc: gdb-patches@sources.redhat.com Message-Id: <20031114193714.872554B3FA@berman.michael-chastain.com> Date: Fri, 14 Nov 2003 19:37:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-11/txt/msg00301.txt.bz2 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? Michael C