From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23423 invoked by alias); 20 Apr 2004 16:34:01 -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 23220 invoked from network); 20 Apr 2004 16:33:51 -0000 Received: from unknown (HELO localhost.redhat.com) (205.151.9.143) by sources.redhat.com with SMTP; 20 Apr 2004 16:33:51 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 93B282B9E; Tue, 20 Apr 2004 12:33:17 -0400 (EDT) Message-ID: <408550CD.5080902@gnu.org> Date: Tue, 20 Apr 2004 16:40:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com, cagney@redhat.com Subject: Re: New test failures - observer.exp, sigaltstack.exp, siginfo.exp References: <20040416151243.GA31255@nevyn.them.org> In-Reply-To: <20040416151243.GA31255@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00109.txt.bz2 (assume I managed to get them to pass on at least one system :-) > sigaltstack.exp fails like this: > > finish > Run till exit from #0 catcher (signal=26) at /opt/src/gdb/src/gdb/testsuite/gdb.base/sigaltstack.c:71 > Warning: > Cannot insert breakpoint 0. > Error accessing memory address 0xffffe420: Input/output error. > (gdb) FAIL: gdb.base/sigaltstack.exp: finish from catch LEAF > > The problem is that the signal trampoline is read-only. We can't set > software breakpoints there. I suspect there is no way to do this portably. > Should we skip it instead, i.e. finish right to the place where the signal > was raised? Kernel bug. Two fixes: - the kernel gets fixed to allow writes to this page -> it should be no different to other read-only text sections - we modify GDB to, when it can't set a return breakpoint, single-step out of the problem > siginfo.exp fails like this: > (gdb) PASS: gdb.base/siginfo.exp: continue to stepi handler > bt > #0 handler (sig=26, info=0xbfffeda0, context=0xbfffee20) at /opt/src/gdb/src/gdb/testsuite/gdb.base/siginfo.c:31 > #1 > #2 main () at /opt/src/gdb/src/gdb/testsuite/gdb.base/siginfo.c:66 > (gdb) PASS: gdb.base/siginfo.exp: backtrace for nexti > step > 32 } /* handler */ > 1: x/i $pc 0x8048411 : pop %ebp > (gdb) step > > Program exited normally. > (gdb) FAIL: gdb.base/siginfo.exp: step out of handler > > I don't know if this is currently expected, or what. It seems like a > bug. This worked on my test PPC system, I'll kfail it conditional on GNU/Linux i386. > 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? Unfortunatly my PPC observer tests were already failing, joel's fixed it :-( Andrew