Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Keith Seitz <keiths@redhat.com>, Hui Zhu <hui_zhu@mentor.com>,
	       gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix dprintf work not right if it is pending
Date: Mon, 08 Apr 2013 18:34:00 -0000	[thread overview]
Message-ID: <5162D6A9.2070706@redhat.com> (raw)
In-Reply-To: <CANFwon11DSoU5jiHX4G7RGuxBOZRaXD6Cth6Ob3X_Z0-TgnPXw@mail.gmail.com>

Hi Hui,

Getting there.

On 04/08/2013 08:19 AM, Hui Zhu wrote:
> +  /* 1 - connect to target 1, that can run breakpoint commands.
> +     2 - create a dprintf, which resolves fine.
> +     3 - disconnect from target 2

This should have been "from target 1".

> +     4 - connect to target 2, that can NOT run breakpoint commands.



> +load_lib gdbserver-support.exp
> +

You're not calling gdbserver directly anymore, so this is no
longer necessary.


> +set testfile "dprintf-pending"
> +set libfile "dprintf-pendshr"
> +set srcfile $testfile.c
> +set libsrc  $srcdir/$subdir/$libfile.c
> +set binfile $objdir/$subdir/$testfile
> +set lib_sl  $objdir/$subdir/$libfile.sl

Please use standard_testfile/standard_output_file.


Instead of these explicit "(without ...)":

> +    "set pending dprintf (without format)" \
...
> +    "set pending dprintf (without symbols)" \
...
> +"single pending dprintf info (without symbols)"
...
> +gdb_test "" ".*x=3.*x=4.*x=3.*" "run to resolved dprintf (without symbols)"

Please use with_test_prefix, like

with_test_prefix "without format" {
  ... group all "without format" bits here, including test setup ...
}

with_test_prefix "without symbols" {
  ... group all "without symbols" bits here ...
}


> +gdb_test "file ${binfile}" ".*Error in re-setting breakpoint.*" "load symbols get without format error"

"load symbols get without format error" is not very correct English
and I find it hard to grok.  I suggest instead "resolved dprintf fails to
be re-set".  No need to mention "without format" here, as that will be
covered by with_test_prefix.

-- 
Pedro Alves


  reply	other threads:[~2013-04-08 14:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  7:39 Hui Zhu
2013-03-22 12:40 ` Yao Qi
2013-03-25  1:00   ` Keith Seitz
2013-03-25  2:14     ` Yao Qi
2013-03-26 14:55     ` Hui Zhu
2013-03-28 17:07       ` Keith Seitz
2013-03-29 15:50         ` Hui Zhu
2013-04-03  3:34           ` Keith Seitz
2013-04-04 18:42             ` Hui Zhu
2013-04-05 18:30             ` Pedro Alves
2013-04-08  7:20               ` Keith Seitz
2013-04-08 17:57                 ` Pedro Alves
2013-04-08  9:34               ` Hui Zhu
2013-04-08 14:35                 ` Hui Zhu
2013-04-08 18:34                   ` Pedro Alves [this message]
2013-04-09 15:28                     ` Hui Zhu
2013-04-09 15:28                       ` Pedro Alves
2013-04-10 15:57                         ` Hui Zhu
2013-04-10 16:12                           ` Hui Zhu
2013-04-11  5:46                             ` Joel Brobecker
2013-04-11 17:03                               ` Pedro Alves
2013-04-12 12:21                                 ` Hui Zhu
2013-03-25  8:25   ` Hui Zhu
2013-03-25  8:28     ` Yao Qi

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=5162D6A9.2070706@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=keiths@redhat.com \
    --cc=teawater@gmail.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