On Wed, 09 Dec 2009 19:31:52 +0100, Oleg Nesterov wrote:
Hmm. it is obvioulsy racy, static volatile unsigned started
is not atomic and thus the main thread can hang doing
while (started THREADS);
not that I think this explains the failure though.
Thanks, fixed (but the problem is
Yes. I straced gdb to be sure it really does PTRACE_SET_DEBUGREF to
use the hardware watchpoint.
There is something strange though. gdb does PTRACE_SINGLESTEP and only
then PTRACE_CONT after watch xxx.
powerpc's data breakpoints are before-access, whereas x86's are
after-access. In
On 12/11, K.Prasad wrote:
On Thu, Dec 10, 2009 at 08:24:36PM +0100, Oleg Nesterov wrote:
Oh well. I spent this day grepping arch/powerpc to understand how
PTRACE_SET_DEBUGREG works and what is the problem. But I am afraid
this time I need a help from someone who understands the hardware
On Fri, Dec 11, 2009 at 04:59:44PM +0100, Oleg Nesterov wrote:
On 12/11, K.Prasad wrote:
Watchpoints (using DABR) through GDB can fail for many reasonsthey
must ideally be set after the program has started execution - to enable
GDB know the size of the variable...else they would resort
On 12/11, Oleg Nesterov wrote:
For those who didn't read the whole thread, the test-case:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/tests/ptrace-tests/tests/watchpoint.c?cvsroot=systemtap
or you can look at
On 12/10, Oleg Nesterov wrote:
On 12/09, CAI Qian wrote:
- Oleg Nesterov o...@redhat.com wrote:
Thanks, but it doesn't fail for me on this machine...
Hmm, it failed for me.
# cd /root/ptrace-tests
# make check
...
FAIL: watchpoint
OMG. Yet another test-case fails
I bet it fails without utrace too? (please don't tell it doesn't ;)
Yes.
Did you see it fails on other ppc64 machines?
No.
Ah. I didn't notice you did biarch-check, not check.
Will take a look later...
Thanks in advance,
CAI Qian
On Thu, Dec 10, 2009 at 08:24:36PM +0100, Oleg Nesterov wrote:
On 12/09, CAI Qian wrote:
- Oleg Nesterov o...@redhat.com wrote:
Thanks, but it doesn't fail for me on this machine...
Hmm, it failed for me.
# cd /root/ptrace-tests
# make check
...
FAIL: watchpoint
On 12/08, caiq...@redhat.com wrote:
This is seen with and without CONFIG_UTRACE.
Good, at least we shouldn't worry about utrace.
FAIL: watchpoint
ppc-dabr-race: ./../tests/ppc-dabr-race.c:141: handler_fail: Assertion `0'
failed.
/bin/sh: line 5: 31750 Aborted ${dir}$tst
This is seen with and without CONFIG_UTRACE.
FAIL: watchpoint
ppc-dabr-race: ./../tests/ppc-dabr-race.c:141: handler_fail: Assertion `0'
failed.
/bin/sh: line 5: 31750 Aborted ${dir}$tst
FAIL: ppc-dabr-race
Are those known issues?
Thanks,
CAI Qian
10 matches
Mail list logo
