From: Andrew Cagney <cagney@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: internal-error: insert_step_resume_breakpoint_at_sal
Date: Tue, 08 Feb 2005 16:57:00 -0000 [thread overview]
Message-ID: <4208EF04.7010603@gnu.org> (raw)
In-Reply-To: <16898.60197.451839.125809@farnswood.snap.net.nz>
Nick Roberts wrote:
> > First thing I'd do is run the sig*.exp tests to see which are failing -
> > if the kernel's working correctly they all pass.
Definitly kernel bugs. See http://sources.redhat.com/gdb/bugs/1702 for
instance.
> Running ./gdb.base/sigall.exp ...
> Running ./gdb.base/sigaltstack.exp ...
> Running ./gdb.base/sigbpt.exp ...
> KFAIL: gdb.base/sigbpt.exp: stepi; stepi out of handler (executed fault insn) (PRMS: gdb/1702)
> KFAIL: gdb.base/sigbpt.exp: stepi bp before segv; stepi out of handler (executed fault insn) (PRMS: gdb/1702)
> KFAIL: gdb.base/sigbpt.exp: stepi bp at segv; stepi out of handler (corrupt pc) (PRMS: gdb/1702)
> KFAIL: gdb.base/sigbpt.exp: stepi bp before and at segv; stepi out of handler (corrupt pc) (PRMS: gdb/1702)
> Running ./gdb.base/siginfo.exp ...
> Running ./gdb.base/signals.exp ...
> KFAIL: gdb.base/signals.exp: override SIGINT (PRMS: gdb/1707)
> Running ./gdb.base/signull.exp ...
> Running ./gdb.base/sigrepeat.exp ...
> Running ./gdb.base/sigstep.exp ...
> KFAIL: gdb.base/sigstep.exp: step on breakpoint, to handler; performing step (PRMS: gdb/1738)
> KFAIL: gdb.base/sigstep.exp: next on breakpoint, to handler; performing next (PRMS: gdb/1738)
> KFAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler; performing continue (PRMS: gdb/1738)
> KFAIL: gdb.base/sigstep.exp: step on breakpoint, to handler entry; performing step (PRMS: gdb/1738)
> KFAIL: gdb.base/sigstep.exp: next on breakpoint, to handler entry; performing next (PRMS: gdb/1738)
> KFAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler entry; performing continue (PRMS: gdb/1738)
>
>
> Note though, that many other tests fail too. What's the simplest way to run an
> individual test? I used:
>
> /home/nick/src/gdb/../dejagnu/runtest -tool gdb GDB=../gdb ./gdb.base/sigbpt.exp
>
> but that can't be right.
It works right :-)
The other way is:
make check RUNTESTFLAGS=sigbpt.exp
(RUNTESTFLAGS gets passed to dejagnu)
Andrew
prev parent reply other threads:[~2005-02-08 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 4:02 Nick Roberts
2005-01-16 10:54 ` Nick Roberts
2005-01-18 18:59 ` Andrew Cagney
2005-01-18 21:53 ` Nick Roberts
2005-01-19 15:55 ` Andrew Cagney
2005-01-20 0:59 ` Nick Roberts
2005-01-20 10:23 ` Dave Korn
2005-01-20 10:58 ` Nick Roberts
2005-01-20 17:07 ` Andrew Cagney
2005-01-21 2:47 ` Nick Roberts
2005-01-24 21:59 ` Andrew Cagney
2005-01-26 10:19 ` Nick Roberts
2005-01-26 16:26 ` Andrew Cagney
2005-01-26 20:48 ` Nick Roberts
2005-01-26 21:39 ` Andrew Cagney
2005-01-27 1:02 ` Nick Roberts
2005-02-06 7:16 ` Andrew Cagney
2005-02-06 7:26 ` Andrew Cagney
2005-02-06 20:11 ` Nick Roberts
2005-02-08 16:57 ` Andrew Cagney [this message]
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=4208EF04.7010603@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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