public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dragos dot tatulea at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/10645] Watchpoints on unreadable memory need no singlestepping Date: Mon, 26 Jul 2010 21:03:00 -0000 [thread overview] Message-ID: <20100726210352.31239.qmail@sourceware.org> (raw) In-Reply-To: <20090916175922.10645.jan.kratochvil@redhat.com> ------- Additional Comments From dragos dot tatulea at gmail dot com 2010-07-26 21:03 ------- This patch: http://sourceware.org/ml/gdb-patches/2009-11/msg00429.html seems to change the behavior of watching an invalid area. Here's what happens now: GNU gdb (GDB) 7.0.50.20100131-cvs Copyright (C) 2010 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". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /media/a/gdb/bugzilla/10645/simple...done. (gdb) start Temporary breakpoint 1 at 0x400478: file simple.c, line 4. Starting program: /media/a/gdb/bugzilla/10645/simple Temporary breakpoint 1, main () at simple.c:4 4 i = 1; (gdb) set debug infrun 1 (gdb) watch *p Hardware watchpoint 2: *p (gdb) c Continuing. infrun: clear_proceed_status_thread (process 13517) infrun: proceed (addr=0xffffffffffffffff, signal=144, step=0) infrun: resume (step=0, signal=0), trap_expected=0 infrun: wait_for_inferior (treat_exec_as_sigtrap=0) infrun: target_wait (-1, status) = infrun: 13517 [process 13517], infrun: status->kind = stopped, signal = SIGTRAP infrun: infwait_normal_state infrun: TARGET_WAITKIND_STOPPED infrun: stop_pc = 0x400498 infrun: stopped by watchpoint infrun: stopped data address = 0x600840 infrun: BPSTAT_WHAT_STOP_NOISY infrun: stop_stepping Hardware watchpoint 2: *p Old value = <unreadable> New value = -443987883 main () at simple.c:7 7 return 0; There's no single stepping anymore (at least for this particular case). Need to investigate why. -- http://sourceware.org/bugzilla/show_bug.cgi?id=10645 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-07-26 21:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-16 17:59 [Bug breakpoints/10645] New: " jan dot kratochvil at redhat dot com 2009-09-16 18:00 ` [Bug breakpoints/10645] " jan dot kratochvil at redhat dot com 2009-09-23 14:45 ` jan dot kratochvil at redhat dot com 2009-09-23 14:46 ` jan dot kratochvil at redhat dot com 2009-11-30 16:36 ` dragos dot tatulea at gmail dot com 2009-11-30 16:37 ` dragos dot tatulea at gmail dot com 2009-11-30 17:29 ` jan dot kratochvil at redhat dot com 2010-07-26 21:03 ` dragos dot tatulea at gmail dot com [this message] 2010-08-26 14:11 ` ppluzhnikov at google dot com [not found] <bug-10645-4717@http.sourceware.org/bugzilla/> 2011-07-31 19:09 ` ppluzhnikov at google dot com 2024-01-07 13:33 ` ssbssa at sourceware dot org
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=20100726210352.31239.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).