From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com, cagney@redhat.com
Subject: Re: New test failures - observer.exp, sigaltstack.exp, siginfo.exp
Date: Tue, 20 Apr 2004 16:40:00 -0000 [thread overview]
Message-ID: <408550CD.5080902@gnu.org> (raw)
In-Reply-To: <20040416151243.GA31255@nevyn.them.org>
(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 <signal handler called>
> #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 <handler+13>: 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
next prev parent reply other threads:[~2004-04-20 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 16:18 Daniel Jacobowitz
2004-04-16 17:02 ` Daniel Jacobowitz
2004-04-17 13:52 ` Joel Brobecker
2004-04-20 16:40 ` Andrew Cagney [this message]
2004-04-20 21:21 ` Daniel Jacobowitz
2004-05-03 19:21 ` Andrew Cagney
2004-05-04 19:46 ` Daniel Jacobowitz
2004-08-08 21:41 ` Daniel Jacobowitz
2004-08-09 13:20 ` Andrew Cagney
2004-04-24 0:03 ` Andrew Cagney
2004-04-23 18:35 ` Daniel Jacobowitz
2004-04-24 0:03 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=408550CD.5080902@gnu.org \
--to=cagney@gnu.org \
--cc=cagney@redhat.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).