From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb@sourceware.org>
Cc: "'Pieter Maljaars'" <pieter.maljaars@altenpts.nl>,
"'Joseph S. Myers'" <joseph@codesourcery.com>,
"'Pedro Alves'" <pedro@codesourcery.com>
Subject: Question about solaris CANNOT_STEP_HW_WATCHPOINTS macro
Date: Fri, 09 Apr 2010 20:07:00 -0000 [thread overview]
Message-ID: <001501cad820$36771f50$a3655df0$@muller@ics-cnrs.unistra.fr> (raw)
The macro
CANNOT_STEP_HW_WATCHPOINTS
is currently only defined at one location
in the whole gdb sources:
gdb/config/i386/nm-i386sol2.h
with the following comment:
/* Solaris x86 2.6 and 2.7 targets have a kernel bug when stepping
over an instruction that causes a page fault without triggering
a hardware watchpoint. The kernel properly notices that it shouldn't
stop, because the hardware watchpoint is not triggered, but it forgets
the step request and continues the program normally.
Work around the problem by removing hardware watchpoints if a step is
requested, GDB will check for a hardware watchpoint trigger after the
step anyway. */
I would like to know if any of the solaris gurus
around knows if this bug is still present in newer version of the solaris
kernel or at which version it has been fixed.
I looked into OpenSolaris sources,
but watchpoint.c (which is where I suspect
hardware watchpoints are handled)
was not updated since OpenSolaris launch in June 2005.
On the other hand, the macro
seems to have been introduced into the configuration file
back in April 2000 (revision 1.3 of current CVS tree).
So this leaves about 5 years for a possible fix inside
the Solaris kernel.
If this bug has been solve before 2.9 version of Solaris,
would it be reasonable to just drop that code out?
Pieter, did you consider that issue when writing the
gdbserver port for Solaris?
Pierre Muller
Pascal language support maintainer for GDB
next reply other threads:[~2010-04-09 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 20:07 Pierre Muller [this message]
2010-04-22 13:56 ` Joel Brobecker
2010-04-22 15:47 ` Pierre Muller
2010-04-22 16:51 ` Peter Schauer
2010-04-23 0:00 ` Joel Brobecker
2010-04-23 0:56 ` Pedro Alves
2010-04-23 3:36 ` Joel Brobecker
2010-04-23 7:42 Pieter Maljaars
2010-04-23 12:42 ` Pierre Muller
2010-04-23 12:59 ` Joel Brobecker
2010-04-23 13:27 ` Pedro Alves
2010-04-23 14:08 ` Joel Brobecker
2010-04-23 16:17 ` Pierre Muller
2010-04-23 14:05 Pieter Maljaars
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='001501cad820$36771f50$a3655df0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=pedro@codesourcery.com \
--cc=pieter.maljaars@altenpts.nl \
/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