Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org,  palves@redhat.com,
	 ak@linux.intel.com,  jan.kratochvil@redhat.com
Subject: Re: [PATCH] record: automatically start recording
Date: Thu, 12 May 2016 13:14:00 -0000	[thread overview]
Message-ID: <8637pnctbv.fsf@gmail.com> (raw)
In-Reply-To: <1459866845-28423-1-git-send-email-markus.t.metzger@intel.com>	(Markus Metzger's message of "Tue, 5 Apr 2016 16:34:05 +0200")

Markus Metzger <markus.t.metzger@intel.com> writes:

Hi Markus,

> Is the added convenience worth a new option or do we want to point users to the
> breakpoint-command solution?
>

I don't think it can justify adding a option in GDB to do that, but I am
open to others' thought.  If people think it is useful to have such
option, see my comments below on the patch,

> +/* The inferior-created observer implementing "set auto-record".  */
> +
> +static void
> +record_inferior_created (struct target_ops *ops, int from_tty)
> +{
> +  if (auto_record_string == auto_record_off)
> +    return;
> +
> +  TRY
> +    {
> +      char command[64];
> +
> +      snprintf (command, sizeof(command), "record %s", auto_record_string);
> +

xsnprintf

> +      execute_command (command, from_tty);
> +    }
> +  CATCH (exception, RETURN_MASK_ALL)
> +    {
> +      warning (_("Could not enable record %s: %s"), auto_record_string,
> +	       exception.message);
> +    }
> +  END_CATCH
> +}
> +

> +
> +# check for btrace support
> +if { [skip_btrace_tests] } { return -1 }
> +

Can we test this option on the target without btrace?  I think we can.
The command/option itself is about restarting recording automatically,
but the record type (full/btrace/bts/pt/) doesn't matter.

-- 
Yao (齐尧)


  parent reply	other threads:[~2016-05-12 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 14:34 Markus Metzger
2016-05-09  7:47 ` Metzger, Markus T
2016-05-09 16:19   ` Eli Zaretskii
2016-05-10  7:32     ` Metzger, Markus T
2016-05-12 13:14 ` Yao Qi [this message]
2016-05-12 13:45   ` Metzger, Markus T

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=8637pnctbv.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=markus.t.metzger@intel.com \
    --cc=palves@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