public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/11320] strange output from "info b" with a syscall catchpoint
Date: Wed, 03 Mar 2010 22:43:00 -0000	[thread overview]
Message-ID: <20100303224326.25356.qmail@sourceware.org> (raw)
In-Reply-To: <20100224170034.11320.tromey@redhat.com>


------- Additional Comments From sergiodj at redhat dot com  2010-03-03 22:43 -------
Hi Tom,

I did a quick test here:

GNU gdb (GDB) Fedora (7.0.1-33.fc12)
Copyright (C) 2009 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-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) catch syscall open
Catchpoint 1 (syscall 'open' [5])
(gdb) info b
Num     Type           Disp Enb Address    What
1       catchpoint     keep y              syscall "open"

The same thing happened when I used a version of GDB built from CVS HEAD.  Did
you do anything before issuing a "catch syscall" command?

-- 


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

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


  reply	other threads:[~2010-03-03 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 17:00 [Bug breakpoints/11320] New: " tromey at redhat dot com
2010-03-03 22:43 ` sergiodj at redhat dot com [this message]
2010-03-04  2:32 ` [Bug breakpoints/11320] " tromey at redhat 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=20100303224326.25356.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).