public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <xdje42@gmail.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Regression for watchpoint-fork.exp  [Re: [PATCH v3 2/5] PR breakpoints/7143 - Watchpoint does not trigger when first set]
Date: Wed, 18 Jun 2014 10:43:00 -0000	[thread overview]
Message-ID: <53A16D4A.70500@redhat.com> (raw)
In-Reply-To: <20140617191850.GA10997@host2.jankratochvil.net>

On 06/17/2014 08:18 PM, Jan Kratochvil wrote:
> On Thu, 20 Mar 2014 14:57:36 +0100, Pedro Alves wrote:
>> Here's what I pushed (nothing else changed).
> 
> 31e77af205cf6564c2bf4c18400b4ca16bdf92cd is the first bad commit
> commit 31e77af205cf6564c2bf4c18400b4ca16bdf92cd
> Author: Pedro Alves <palves@redhat.com>
> Date:   Thu Mar 20 13:26:32 2014 +0000
>     PR breakpoints/7143 - Watchpoint does not trigger when first set
> 
> PASS kernel-3.14.6-200.fc20.x86_64
> FAIL kernel-3.13.10-200.dentrybuflen.fc20.x86_64
> 
> continue^M
> Continuing.^M
> main () at ./gdb.threads/watchpoint-fork-st.c:50^M
> 50        forkoff (1);^M
> Couldn't write debug register: Invalid argument.^M

Odd.

> (gdb) FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the first fork
> 
> Being tested for default linux-nat.
> 
> That 'dentrybuflen' patch should not matter.  I did not check which Linux
> kernels are / are not affected by the regression but it would be probably
> better to make the GDB behavior more Linux kernel compatible.

Yes, though off hand I'm clueless on what's going on.

-- 
Pedro Alves

  reply	other threads:[~2014-06-18 10:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  1:10 [PATCH v3 0/5] Fix lost events, and handle multiple step-overs Pedro Alves
2014-03-07  1:10 ` [PATCH v3 4/5] Handle " Pedro Alves
2014-03-07  1:10 ` [PATCH v3 3/5] Fix for even more missed events; eliminate thread-hop code Pedro Alves
2014-03-07  1:10 ` [PATCH v3 5/5] Make signal-while-stepping-over-bp-other-thread.exp run against remote targets too Pedro Alves
2014-03-07  1:10 ` [PATCH v3 2/5] PR breakpoints/7143 - Watchpoint does not trigger when first set Pedro Alves
2014-03-16  3:41   ` Doug Evans
2014-03-17 17:11     ` Pedro Alves
2014-03-19 16:52       ` Doug Evans
2014-03-20 13:58         ` Pedro Alves
2014-03-20 13:57       ` Pedro Alves
2014-06-17 19:18         ` Regression for watchpoint-fork.exp [Re: [PATCH v3 2/5] PR breakpoints/7143 - Watchpoint does not trigger when first set] Jan Kratochvil
2014-06-18 10:43           ` Pedro Alves [this message]
2014-06-19 13:43           ` Jan Kratochvil
2014-06-19 15:02             ` Pedro Alves
2014-06-19 16:56               ` Pedro Alves
2014-06-19 17:00                 ` Jan Kratochvil
2014-06-20 16:53                   ` [PATCH] x86 Linux watchpoints: Couldn't write debug register: Invalid, argument Pedro Alves
2014-06-20 17:45                     ` Tom Tromey
2014-06-20 17:52                       ` Pedro Alves
2014-06-20 17:53                         ` Tom Tromey
2014-06-22 18:31                     ` Jan Kratochvil
2014-06-23 17:41                       ` Pedro Alves
2014-06-23 17:44                         ` Pedro Alves
2014-03-07  1:10 ` [PATCH v3 1/5] Fix missing breakpoint/watchpoint hits, eliminate deferred_step_ptid Pedro Alves
2014-03-20 13:59 ` [PUSHED] Re: [PATCH v3 0/5] Fix lost events, and handle multiple step-overs Pedro Alves

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=53A16D4A.70500@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=xdje42@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).