From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, cagney@redhat.com
Subject: Re: New test failures - observer.exp, sigaltstack.exp, siginfo.exp
Date: Fri, 23 Apr 2004 18:35:00 -0000 [thread overview]
Message-ID: <20040423181514.GA15437@nevyn.them.org> (raw)
In-Reply-To: <40895A36.70005@gnu.org>
On Fri, Apr 23, 2004 at 02:02:30PM -0400, Andrew Cagney wrote:
> >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?
>
> Which exact kernel version? As I mentioned in another post, this works
> for me ....
2.6.5. If you're using a 2.4-era kernel, it probably does not place
the sigreturn trampoline in the vsyscall DSO area.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-04-23 18:15 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
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 [this message]
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=20040423181514.GA15437@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=cagney@redhat.com \
--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).