public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@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: Thu, 19 Jun 2014 13:43:00 -0000	[thread overview]
Message-ID: <20140619134330.GA14567@host2.jankratochvil.net> (raw)
In-Reply-To: <20140617191850.GA10997@host2.jankratochvil.net>

[-- Attachment #1: Type: text/plain, Size: 2831 bytes --]

On Tue, 17 Jun 2014 21:18:50 +0200, 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

That was a red herring, in fact it was due to different GCC.

(gdb) disas marker
Dump of assembler code for function marker:
   0x0000000000400826 <+0>:	push   %rbp
   0x0000000000400827 <+1>:	mov    %rsp,%rbp
=> 0x000000000040082a <+4>:	pop    %rbp
   0x000000000040082b <+5>:	retq   
End of assembler dump.

ptrace(PTRACE_POKEUSER, 24574, offsetof(struct user, u_debugreg), 0x40082a) = -1 EINVAL (Invalid argument)

New GDB in the 'hbreak' case does not align the breakpoint address.
Attaching gzipped gdb.threads/watchpoint-fork-parent-st
from gcc-4.9.0-9.fc21.x86_64.


Jan


../gdb gdb.threads/watchpoint-fork-parent-st -ex 'set pagination off' -ex start -ex 'hbreak marker' -ex 'watch var' -ex c -ex c -ex c
GNU gdb (GDB) 7.8.50.20140619-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gdb.threads/watchpoint-fork-parent-st...done.
Temporary breakpoint 1 at 0x400836: file ./gdb.threads/watchpoint-fork-st.c, line 43.
Starting program: /home/jkratoch/redhat/gdb-test-f20-noasan/gdb/testsuite/gdb.threads/watchpoint-fork-parent-st 

Temporary breakpoint 1, main () at ./gdb.threads/watchpoint-fork-st.c:43
43	  setbuf (stdout, NULL);
Hardware assisted breakpoint 2 at 0x40082a: file ./gdb.threads/watchpoint-fork-st.c, line 33.
Hardware watchpoint 3: var
Continuing.
main: 26352

Breakpoint 2, marker () at ./gdb.threads/watchpoint-fork-st.c:33
33	}
Continuing.
Hardware watchpoint 3: var

Old value = 0
New value = 1
main () at ./gdb.threads/watchpoint-fork-st.c:50
50	  forkoff (1);
Continuing.
main () at ./gdb.threads/watchpoint-fork-st.c:50
50	  forkoff (1);
Couldn't write debug register: Invalid argument.
(gdb) _

[-- Attachment #2: watchpoint-fork-parent-st.gz --]
[-- Type: application/gzip, Size: 4723 bytes --]

  parent reply	other threads:[~2014-06-19 13: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 1/5] Fix missing breakpoint/watchpoint hits, eliminate deferred_step_ptid 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
2014-06-19 13:43           ` Jan Kratochvil [this message]
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 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 3/5] Fix for even more missed events; eliminate thread-hop code 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=20140619134330.GA14567@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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).