Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: tests for MI commands
Date: Sun, 24 Jul 2005 21:19:00 -0000	[thread overview]
Message-ID: <20050724211946.GB798@nevyn.them.org> (raw)
In-Reply-To: <17117.55351.716393.763492@farnswood.snap.net.nz>

On Wed, Jul 20, 2005 at 04:51:03PM +1200, Nick Roberts wrote:
> 
> This patch provides tests for the recent changes to -var-update and
> -var-list-children.  I have also revised the test for stack-list-locals
> so that it properly tests the --simple-values option.
> 
> There is no test for "-var-update --simple-values" as I could not get it
> to behave differently for "-var-update --all-values".  I think this is
> because the changelist only consists of simple types; if it is complex
> its `value' is deemed not have changed.

Thanks.  The tests themselves look roughly fine, but:

> 	* gdb.mi/mi-var-child.exp: Adapt tests for extra elements and use
> 	them for tests for "-var-update --no-values" and
> 	"-var-update --all-values".  
> 	Add test for "-var-list-children --simple-values.

Missing quote mark.

> *************** do_children_tests (void)
> *** 227,232 ****
> --- 227,234 ----
>     struct_declarations.long_array[9] = 1234;
>   
>     weird->func_ptr = nothing;
> +   struct_declarations.long_array[10] = 3456;
> +   struct_declarations.long_array[11] = 5678;
>   
>     /* Struct/pointer/array tests */
>     a0 = '0';
> 

You had a bunch of changes that only were needed because you added
initializations between weird->func_ptr = nothing and a0 = '0'; why not
put them above it, with the others?  There might be some problem with
that I haven't seen...

> ! # Step over "weird->func_ptr = nothing;"
> ! set line_dct_a0_0 [gdb_get_line_number "a0 = '0';"]
>   mi_step_to do_children_tests {} {.*var-cmd.c} \
> !     $line_dct_a0_0 "step \$line_dct_a0_0"

> --- 833,842 ----

> ! # Step over weird->func_ptr = nothing;
>   mi_step_to do_children_tests {} {.*var-cmd.c} \
> !     [expr $line_dct_nothing + 1] "step \$line_dct_nothing + 1"

Please don't do math on line numbers; gdb_get_line_number helps make
test cases more robust against changes in the test source.

> + # Step overstruct_declarations.long_array[10] = 3456;

> +  "update  all vars struct_declarations.long_array.10 changed, don't print values."

Missing space; extra space.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-07-24 21:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20  4:51 Nick Roberts
2005-07-24 21:19 ` Daniel Jacobowitz [this message]
2005-07-26 23:31   ` Nick Roberts
2005-07-27  0:27     ` Daniel Jacobowitz
2005-07-27  3:04       ` Nick Roberts
2005-07-27  3:55         ` Daniel Jacobowitz
2005-07-27 11:46           ` Nick Roberts
2005-07-27 12:50             ` Bob Rossi
2005-07-27 20:52               ` Nick Roberts
2005-07-27 21:49                 ` Daniel Jacobowitz
2005-07-27 22:09                   ` Nick Roberts
2005-07-27 21:03             ` Mark Kettenis
2005-07-27 22:23               ` Nick Roberts
2005-07-28  0:08                 ` Paul Gilliam
2005-07-28  0:18                 ` Stan Shebs
2005-07-28  0:21                 ` Daniel Jacobowitz
2005-07-28  1:39                   ` Nick Roberts
2005-07-31 22:11                     ` Daniel Jacobowitz
2005-07-31 23:32                       ` Nick Roberts
2005-08-01  1:55                         ` Daniel Jacobowitz
2005-07-27 21:25             ` Mark Kettenis
2005-07-29  7:32           ` Nick Roberts
2005-07-31 21:25             ` Daniel Jacobowitz
2005-07-31 23:32               ` Nick Roberts
2005-08-01  1:57                 ` Daniel Jacobowitz

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=20050724211946.GB798@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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