public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/10120] Should catchpoints be shown with type 'catchpoint' in 'info breakpoints' ?
Date: Thu, 30 Apr 2009 22:44:00 -0000	[thread overview]
Message-ID: <20090430224407.25289.qmail@sourceware.org> (raw)
In-Reply-To: <20090430223440.10120.pedro@codesourcery.com>


------- Additional Comments From pedro at codesourcery dot com  2009-04-30 22:44 -------
The second comment was meant to be a new PR...  It is now PR10121.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Does the user care that some|Should catchpoints be shown
                   |catchpoints happen to be    |with type 'catchpoint' in
                   |implemented with            |'info breakpoints' ?
                   |breakpoints?                |


http://sourceware.org/bugzilla/show_bug.cgi?id=10120

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-04-30 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 22:34 [Bug breakpoints/10120] New: " pedro at codesourcery dot com
2009-04-30 22:39 ` [Bug breakpoints/10120] Does the user care that some catchpoints happen to be implemented with breakpoints? pedro at codesourcery dot com
2009-04-30 22:44 ` pedro at codesourcery dot com [this message]
     [not found] <bug-10120-4717@http.sourceware.org/bugzilla/>
2022-01-03 13:33 ` [Bug breakpoints/10120] Should catchpoints be shown with type 'catchpoint' in 'info breakpoints' ? ssbssa at sourceware dot org
2024-01-07 13:23 ` 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=20090430224407.25289.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: 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).