public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/7143] Watchpoint does not trigger when first set Date: Thu, 29 May 2014 15:02:00 -0000 [thread overview] Message-ID: <bug-7143-4717-LS2Jc2mbex@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-7143-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=7143 --- Comment #14 from Pedro Alves <palves at redhat dot com> --- "set debug target" might help though, it shows the target_insert_breakpoint/target_remove_breakpoint calls. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-29 15:02 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-7143-4717@http.sourceware.org/bugzilla/> 2012-01-25 16:29 ` tromey at redhat dot com 2012-01-25 16:34 ` tromey at redhat dot com 2012-01-25 16:58 ` palves at redhat dot com 2012-03-30 13:46 ` eager at eagercon dot com 2012-09-25 21:09 ` palves at redhat dot com 2014-02-24 17:23 ` palves at redhat dot com 2014-03-20 13:49 ` cvs-commit at gcc dot gnu.org 2014-03-20 13:53 ` palves at redhat dot com 2014-05-20 18:02 ` cvs-commit at gcc dot gnu.org 2014-05-29 13:28 ` brobecker at gnat dot com 2014-05-29 15:01 ` palves at redhat dot com 2014-05-29 15:02 ` palves at redhat dot com [this message] 2014-05-29 17:47 ` brobecker at adacore dot com 2014-05-29 18:04 ` palves at redhat dot com 2014-05-29 18:35 ` brobecker at adacore dot com 2014-05-29 22:22 ` palves at redhat dot com 2014-05-30 16:09 ` palves at redhat dot com 2014-05-30 16:21 ` brobecker at adacore dot com 2014-08-19 17:19 ` cvs-commit at gcc dot gnu.org [not found] <20010311215800.7143.chastain@redhat.com> 2009-01-09 16:48 ` naaaag at gmail dot com
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=bug-7143-4717-LS2Jc2mbex@http.sourceware.org/bugzilla/ \ --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).