This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1736: Can not set breakpoints in the vsyscall page
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 18 Jul 2005 18:18:01 -0000
- Subject: Re: gdb/1736: Can not set breakpoints in the vsyscall page
- Reply-to: Mark Kettenis <mark dot kettenis at xs4all dot nl>
The following reply was made to PR external/1736; it has been noted by GNATS.
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-gnats@sourceware.org
Cc:
Subject: Re: gdb/1736: Can not set breakpoints in the vsyscall page
Date: Mon, 18 Jul 2005 20:17:16 +0200 (CEST)
[ Adding some blurb to make it possible to kfail for *-*-openbsd*. ]
OpenBSD has a very similar issue. Here the "signal trampoline" lives
on a page that is mapped read-only at a random location in user space.
This means that setting breakpoints is impossible too. It's probably
not desirable to change this in OpenBSD, so GDB should really fallback
to single-stepping.
It's likely that other BSD's have the same issue, although modern
versions of NetBSD shouldn't be affected since their signal
trampolines live in libc.
Mark