From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: pieter.maljaars@altenpts.nl,
Peter.Schauer@regent.e-technik.tu-muenchen.de,
gdb@sourceware.org,
"'Joseph S. Myers'" <joseph@codesourcery.com>,
'Pedro Alves' <pedro@codesourcery.com>
Subject: Re: Question about solaris CANNOT_STEP_HW_WATCHPOINTS macro
Date: Fri, 23 Apr 2010 12:59:00 -0000 [thread overview]
Message-ID: <20100423125909.GK13204@adacore.com> (raw)
In-Reply-To: <002301cae2e2$34a4c3e0$9dee4ba0$@muller@ics-cnrs.unistra.fr>
> I reproduced Pieter's results and filed
> a bug report:
> http://sourceware.org/bugzilla/show_bug.cgi?id=11531
Just a small suggestion when filing bug reports, if you can - it makes
it easier to figure out the problem being reported is when showing what
is happening and what should have happened. Also, confirming the command
used to build the program is also useful...
Note that, on my end, it looked like the CANNOT_STEP_HW_WATCHPOINTS
macro had no effect, so I am not sure I understand the PR. But I
did the testing on x86 as opposed to x86_64, so perhaps that makes
a difference. Or maybe the OS version does - I tested on version 8.
I don't know if we have a machine that runs version 10.
--
Joel
next prev parent reply other threads:[~2010-04-23 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 7:42 Pieter Maljaars
2010-04-23 12:42 ` Pierre Muller
2010-04-23 12:59 ` Joel Brobecker [this message]
2010-04-23 13:27 ` Pedro Alves
2010-04-23 14:08 ` Joel Brobecker
2010-04-23 16:17 ` Pierre Muller
-- strict thread matches above, loose matches on Subject: below --
2010-04-23 14:05 Pieter Maljaars
2010-04-09 20:07 Pierre Muller
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
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=20100423125909.GK13204@adacore.com \
--to=brobecker@adacore.com \
--cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=pedro@codesourcery.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--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