From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: PR8554: New command to save breakpoints to a file
Date: Fri, 09 Apr 2010 17:23:00 -0000 [thread overview]
Message-ID: <201004091823.31659.pedro@codesourcery.com> (raw)
In-Reply-To: <m3aatcob1g.fsf@fleche.redhat.com>
On Friday 09 April 2010 17:17:31, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>
> Pedro> (I finished this instead of dumping it.)
>
> Thanks. I do like this approach.
>
> Pedro> Add a new save-breakpoints command to save breakpoint definitions
> Pedro> to a file.
>
> I'd personally prefer "save breakpoints", with a space, and make
> save-tracepoints a deprecated alias for "save tracepoints". What do you
> (and others) think of this? I tend to like simple commands with spaces,
> especially when a subcommand comes along.
Fine with me.
> Pedro> The new breakpoint_ops->print_recreate method implementation for
> Pedro> all catchpoints is always mostly a simplified version of
> Pedro> breakpoint_ops->print_mention method.
>
> Could you enlighten me on a historical (?) point? Why is it that some
> kinds of breakpoints have methods like this and some do not? Is this an
> incomplete transition, or an intentional design choice?
I think the former. breakpoint_ops was added initialy for some
catchpoints in 2003. I wasn't around then.
>
> Pedro> + if (tp->thread != -1)
> Pedro> + fprintf_unfiltered (fp, " thread %d", tp->thread);
> Pedro> +
> Pedro> + if (tp->task != 0)
> Pedro> + fprintf_unfiltered (fp, " task %d", tp->task);
> Pedro> +
> Pedro> if (tp->cond_string)
> Pedro> fprintf_unfiltered (fp, " if %s", tp->cond_string);
>
> I don't think this syntax will work for a conditional catchpoint.
> Our Python-based implementation gets this wrong as well. I think you
> need a separate "cond" command in the output.
You're right. It works for breakpoints, but not for other types:
(top-gdb) b main thread 1 if 0
Breakpoint 4 at 0x4572b3: file ../../src/gdb/gdb.c, line 28.
(top-gdb) watch main thread 1 if 0
Junk at end of command.
The `b *0xaddr thread 1 if 0' syntax may not work for
some languages.
I'll post an updated patch, once I update it. :-)
--
Pedro Alves
next prev parent reply other threads:[~2010-04-09 17:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 2:41 Pedro Alves
2010-04-09 16:17 ` Tom Tromey
2010-04-09 17:23 ` Pedro Alves [this message]
2010-04-10 4:10 ` Sergio Durigan Junior
2010-04-12 18:15 ` Pedro Alves
2010-04-15 17:52 ` Michael Snyder
2010-04-15 18:27 ` Pedro Alves
2010-04-15 18:46 ` Michael Snyder
2010-04-15 18:53 ` Pedro Alves
2010-04-15 18:58 ` Michael Snyder
2010-04-15 19:58 ` Pedro Alves
2010-04-15 22:49 ` Michael Snyder
2010-04-15 22:52 ` Michael Snyder
2010-04-15 22:58 ` Michael Snyder
2010-04-15 23:05 ` Pedro Alves
2010-04-15 23:15 ` Michael Snyder
2010-04-15 23:25 ` Pedro Alves
2010-05-05 8:28 ` Hui Zhu
2010-04-15 23:14 ` Michael Snyder
2010-04-15 23:20 ` Pedro Alves
2010-04-15 23:01 ` Pedro Alves
2010-04-15 18:59 ` Stan Shebs
2010-04-15 19:10 ` Pedro Alves
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=201004091823.31659.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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