Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH: gdb/mi] -stack-list-locals testcase
Date: Tue, 06 Jan 2004 01:07:00 -0000	[thread overview]
Message-ID: <3FFA0A4A.1020908@gnu.org> (raw)
In-Reply-To: <16377.64533.42018.863120@nick.uklinux.net>

>  > Nick, just the testcase is missing.  Suggest tweaking "mi-stack.exp" 
>  > (you do not need to tweak mi[12]-stack.exp since they test older protocols).
> 
> mi-stack.exp had three fails to start with. Replacing line=\"7\" with
> line=\"8\" and "-exec-next 3" with "-exec-next 4" removed them.
> 
> I have added one simple test for `-stack-list-locals 2' that seems to
> work. It does not test complex data types but this would require changing
> basics.c, which is probably not worth it.
> 
> Andrew, if you tell me that this patch does the right thing, then I'll do one
> for -var-list-children.
> 
> Nick
> 
> 
> *** mi-stack.exp.~1.10.~	2002-11-05 15:43:18.000000000 +0000
> --- mi-stack.exp	2004-01-05 23:38:27.000000000 +0000
> ***************
> *** 57,63 ****
>       # -stack-list-frames 1 3
>   
>       mi_gdb_test "231-stack-list-frames" \
> ! 	    "231\\^done,stack=\\\[frame=\{level=\"0\",addr=\"$hex\",func=\"callee4\",file=\".*basics.c\",line=\"8\"\},frame=\{level=\"1\",addr=\"$hex\",func=\"callee3\",.*\},frame=\{level=\"2\",addr=\"$hex\",func=\"callee2\",.*\},frame=\{level=\"3\",addr=\"$hex\",func=\"callee1\",.*\},frame=\{level=\"4\",addr=\"$hex\",func=\"main\",.*\}\\\]" \
>                   "stack frame listing"
>       mi_gdb_test "232-stack-list-frames 1 1" \
>   	    "232\\^done,stack=\\\[frame=\{level=\"1\",addr=\"$hex\",func=\"callee3\",.*\}\\\]" \
> --- 57,63 ----
>       # -stack-list-frames 1 3
>   
>       mi_gdb_test "231-stack-list-frames" \
> ! 	    "231\\^done,stack=\\\[frame=\{level=\"0\",addr=\"$hex\",func=\"callee4\",file=\".*basics.c\",line=\"7\"\},frame=\{level=\"1\",addr=\"$hex\",func=\"callee3\",.*\},frame=\{level=\"2\",addr=\"$hex\",func=\"callee2\",.*\},frame=\{level=\"3\",addr=\"$hex\",func=\"callee1\",.*\},frame=\{level=\"4\",addr=\"$hex\",func=\"main\",.*\}\\\]" \
>                   "stack frame listing"
>       mi_gdb_test "232-stack-list-frames 1 1" \
>   	    "232\\^done,stack=\\\[frame=\{level=\"1\",addr=\"$hex\",func=\"callee3\",.*\}\\\]" \

This test (and the rest of mi-stack.exp) is passing on a PPC/NetBSD gcc 
2.96 stabs system.  We'll need to look at it more carefully (or check 
michaelc's test matrix) to see why there's a failure.  MI is more strict 
  with its test results.

> ***************
> *** 156,162 ****
>                   "stack locals listing 0"
>   
>   # step until A, B, C, have some reasonable values.
> ! send_gdb "-exec-next 3\n"
>   gdb_expect {
>       -re "\\^running\r\n${mi_gdb_prompt}\\*stopped,reason=\"end-stepping-range\",thread-id=\"\[01\]\",frame=\{addr=\"$hex\",func=\"callee4\",args=\\\[\\\],file=\".*basics.c\",line=\"13\"\}\r\n$mi_gdb_prompt$" {
>   	pass "next's in callee4"
> --- 156,162 ----
>                   "stack locals listing 0"
>   
>   # step until A, B, C, have some reasonable values.
> ! send_gdb "-exec-next 4\n"
>   gdb_expect {
>       -re "\\^running\r\n${mi_gdb_prompt}\\*stopped,reason=\"end-stepping-range\",thread-id=\"\[01\]\",frame=\{addr=\"$hex\",func=\"callee4\",args=\\\[\\\],file=\".*basics.c\",line=\"13\"\}\r\n$mi_gdb_prompt$" {
>   	pass "next's in callee4"
> ***************
> *** 168,173 ****
> --- 168,177 ----
>   	    "232\\^done,locals=\\\[\{name=\"A\",value=\"1\"\},\{name=\"B\",value=\"2\"\},\{name=\"C\",value=\"3\"\}\\\]" \
>                   "stack locals listing 1"
>   
> +     mi_gdb_test "232-stack-list-locals 2" \
> + 	    "232\\^done,locals=\\\[\{name=\"A\",type=\"int\",value=\"1\"\},\{name=\"B\",type=\"int\",value=\"2\"\},\{name=\"C\",type=\"int\",value=\"3\"\}\\\]" \
> +                 "stack locals listing 2"
> + 

Yes, just like that.

Andrew


>       mi_gdb_test "234-stack-list-locals" \
>   	    "234\\^error,msg=\"mi_cmd_stack_list_locals: Usage.*PRINT_VALUES.*\"" \
>   	    "stack locals listing wrong"
> 



  reply	other threads:[~2004-01-06  1:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-23  0:16 RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-11-26  0:48 ` Andrew Cagney
2003-12-02  3:14   ` RFC (gdb/mi): -stack-list-locals + PATCH Nick Roberts
2003-12-09  2:42     ` RFC (gdb/mi): -stack-list-locals + REVISED PATCH Nick Roberts
2003-12-10 17:56       ` Andrew Cagney
2003-12-10 22:26         ` Jason Molenda
2003-12-12 20:51         ` RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-12-12 21:09           ` David Carlton
2003-12-17  2:29             ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Nick Roberts
2003-12-17  2:32               ` David Carlton
2003-12-17 18:51                 ` [PATCH: gdb/mi] -stack-list-locals Nick Roberts
2003-12-17 21:21                   ` David Carlton
2003-12-17 18:05               ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Eli Zaretskii
2004-01-05 21:43               ` Andrew Cagney
2004-01-06  0:14                 ` [PATCH: gdb/mi] -stack-list-locals testcase Nick Roberts
2004-01-06  1:07                   ` Andrew Cagney [this message]
2004-01-07 16:31                     ` Andrew Cagney
2004-01-07 17:34                       ` Mark Kettenis
2004-01-07 17:40                         ` Daniel Jacobowitz
2003-12-12 23:01           ` RFC (gdb/mi): -stack-list-locals Jason Molenda
2004-01-06  1:12 [PATCH: gdb/mi] -stack-list-locals testcase Michael Elizabeth Chastain
2004-01-07 21:06 Michael Elizabeth Chastain
2004-01-07 23:47 ` Nick Roberts

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=3FFA0A4A.1020908@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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