Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address

Edjunior Barbosa Machado
2012-08-03T12:09:55Z

On 08/03/2012 08:22 AM, Jan Kratochvil wrote:
> On Fri, 03 Aug 2012 02:14:34 +0200, Edjunior Barbosa Machado wrote:
>> FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork
>> FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork
>> FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork
>> FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork
>> FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish
>
> most probably it is due to ppc-linux-nat.c and s390-nat.c changes still left
> on archer-jankratochvil-watchpoint3 and not yet upstreamed with the x86* post
> [patch 1/2] Fix watchpoints across fork #2
> http://sourceware.org/ml/gdb-patches/2012-01/msg00748.html
>
> It is not a regression, I think it is OK for 7.6 (+Red Hat branches can get
> a backport for 7.5).
>
>
> Sorry,
> Jan
>

Thanks Jan for pointing this out, but actually, this looks a bit different without the patch fixing PR 14100:

FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the first fork (GDB internal error)
PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the first fork
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork (GDB internal error)
PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork
PASS: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish

--
Edjunior