Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix create pending breakpoint handle extra_string issue if not parse_condition_and_thread
Date: Mon, 25 Mar 2013 00:53:00 -0000	[thread overview]
Message-ID: <514EEB43.6040101@redhat.com> (raw)
In-Reply-To: <514E8D6C.2010606@mentor.com>

On 03/23/2013 10:21 PM, Hui Zhu wrote:

> -break-insert -f -c k>0 "pendfunc1 if k == 0"
> &"Function \"pendfunc1\" not defined.\n"
> ^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="<PENDING>",pending="pendfunc1
> if k == 0",cond="k>0",times="0",original-location="pendfunc1 if k == 0"}

IMO, this should not be permitted at all. Two reasons:

1) We could argue about which condition is correct to keep.
2) The MI specification does not say anything about permitting this type 
of usage. [I would therefore argue it is illegal.]

Likewise for "thread" (and "task", but there is no task parameter for 
create_breakpoint for some reason).

Ideally an error should be issued when the breakpoint is set:

-break-insert -c "argc > 1" "main if argc > 2"
^error,msg="Garbage 'if argc > 2' at end of command"

Please remember to submit a test case (or cases) with patches whenever 
possible.

Keith


  reply	other threads:[~2013-03-24 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 12:05 Hui Zhu
2013-03-25  0:53 ` Keith Seitz [this message]
2013-03-25  7:54   ` Hui Zhu
2013-03-25 16:14     ` Yao Qi
2013-03-25 16:27       ` Hui Zhu
2013-03-25 19:32     ` Tom Tromey
2013-03-25 19:58       ` Keith Seitz
2013-03-26 11:16         ` Hui Zhu
2013-04-05 19:18         ` Pedro Alves
2013-04-08  7:56           ` Keith Seitz
2013-04-08 17:54             ` 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=514EEB43.6040101@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.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