From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6110 invoked by alias); 16 Apr 2004 15:12:45 -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 6085 invoked from network); 16 Apr 2004 15:12:44 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 16 Apr 2004 15:12:44 -0000 Received: from drow by nevyn.them.org with local (Exim 4.31 #1 (Debian)) id 1BEV1H-0008Gj-KP; Fri, 16 Apr 2004 11:12:43 -0400 Date: Fri, 16 Apr 2004 16:18:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Cc: cagney@redhat.com Subject: New test failures - observer.exp, sigaltstack.exp, siginfo.exp Message-ID: <20040416151243.GA31255@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com, cagney@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-04/txt/msg00090.txt.bz2 These new tests are all failing on my i686-pc-linux-gnu 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? 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. 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? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer