From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24883 invoked by alias); 16 Apr 2004 17:02:36 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24874 invoked from network); 16 Apr 2004 17:02:34 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 16 Apr 2004 17:02:34 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 0253947D63; Fri, 16 Apr 2004 10:02:34 -0700 (PDT) Date: Sat, 17 Apr 2004 13:52:00 -0000 From: Joel Brobecker To: gdb@sources.redhat.com, cagney@redhat.com Subject: Re: New test failures - observer.exp, sigaltstack.exp, siginfo.exp Message-ID: <20040416170234.GC22414@gnat.com> References: <20040416151243.GA31255@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040416151243.GA31255@nevyn.them.org> User-Agent: Mutt/1.4i X-SW-Source: 2004-04/txt/msg00092.txt.bz2 > observer.exp fails like this: > > call observer_notify_normal_stop () > too few arguments in function call > (gdb) PASS: gdb.gdb/observer.exp: sending notification (one observer) > > Then all the counters are wrong, since the function call didn't happen. > That's definitely a problem in the test script, since observer_notify_normal_stop > takes an argument; is this not a fatal condition on some other target? I am working on this part. I will send a couple of patches soon. -- Joel