From: Kevin Pouget <kevin.pouget@gmail.com>
To: pmuldoon@redhat.com
Cc: gdb@sourceware.org
Subject: Re: GDB Python API: stop/continue after breakpoint
Date: Mon, 21 Mar 2011 15:11:00 -0000 [thread overview]
Message-ID: <AANLkTikgGfSu3mwQD1-ohKQ-F1Q7Db5XmoKnuKigxWfL@mail.gmail.com> (raw)
In-Reply-To: <m3d3lkr119.fsf@redhat.com>
> (gdb) py b.silent = True
very nice! I was just reading an old post
http://sourceware.org/ml/gdb/2007-04/msg00127.html about a plugin vs
scripting interface, Python finally get the point, it's now easier to
write a Python script which handles breakpoints than a GDB patch!
> There might be a case for setting the breakpoint to 'silent' in the
> breakpoint constructor:
>
> python b = gdb.Breakpoint("hello.c:5", internal=True, silent=True)
>
> or just making internal breakpoints silent by default.
>
> I'll implement either. What do you think?
from my perspective, _internal breakpoints_ should be silent by
default, because they're 'internal', as their name says.
Option 1) is quite similar `b.silent`, so it's up to you
Cordially,
Kevin
prev parent reply other threads:[~2011-03-21 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 16:09 Kevin Pouget
2011-03-11 16:25 ` Phil Muldoon
[not found] ` <AANLkTin_a87WgchmZnzi9_XX4DXh8q-r3P7EyyDAzTA4@mail.gmail.com>
2011-03-11 17:52 ` Kevin Pouget
2011-04-20 14:59 ` Kevin Pouget
2011-04-20 15:15 ` Phil Muldoon
2011-04-20 15:39 ` Tom Tromey
2011-04-21 13:01 ` Kevin Pouget
[not found] ` <BANLkTinwMfsxA24q-5ekbapVdM_OP6rOsQ@mail.gmail.com>
2011-04-21 14:32 ` Kevin Pouget
2011-04-20 15:20 ` Tom Tromey
2011-03-21 14:20 ` Kevin Pouget
2011-03-21 14:39 ` Phil Muldoon
2011-03-21 15:11 ` Kevin Pouget [this message]
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=AANLkTikgGfSu3mwQD1-ohKQ-F1Q7Db5XmoKnuKigxWfL@mail.gmail.com \
--to=kevin.pouget@gmail.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.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).