Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] varobj deletion after the binary has changed
Date: Wed, 31 Jan 2007 21:29:00 -0000	[thread overview]
Message-ID: <17857.2617.164646.935952@kahikatea.snap.net.nz> (raw)
In-Reply-To: <45C0B042.9040308@st.com>

 >    /* sanity check: have we been passed a pointer? */
 >    if (changelist == NULL)
 > -    return -1;
 > +    return WRONG_PARAM;
 >  
 >    /*  Only root variables can be updated... */
 >    if (!is_root_p (*varp))
 >      /* Not a root var */
 > -    return -1;
 > +    return WRONG_PARAM;
 > +
 > +  if (!(*varp)->root->is_valid)
 > +    return INVALID;

OK I hadn't noticed the distinction between WRONG_PARAM and INVALID.  I think
it would be better to throw an error in the case of WRONG_PARAM, otherwise
changes to leaf values may go unnoticed.  But this is a separate change.

I've not checked the test but I think the English could be improved and
different names used:

>  ...
> # Verify that once binary file has changed, GDB correctly handles
> # previously defined MI variables.

# Verify that once binary file has changed, GDB correctly handles
# previously defined MI variable objects.

 > ...
 > #
 > # reload the same binary
 > # global variable must be keeped, other invalidated

 # Reload the same binary.
 # Global variable should remain, local should be invalidated.

 > #
 > mi_delete_breakpoints
 > mi_gdb_load ${binfile_bis}
 > mi_runto main

 > # Check local variable are "invalid"

 # Check local variable is "invalid"

 > mi_gdb_test "-var-update linteger" \
 > 	"\\^done,changelist=\\\[\{name=\"linteger\",in_scope=\"invalid\"\}\\\]" \
 > 	"linteger not anymore in scope due to binary changes"
 > 
 > mi_gdb_test "-var-info-type linteger" \
 > 	"\\^done,type=\"\"" \
 > 	"not type for invalid variable linteger"

 "no type for invalid variable linteger (1)"

 > # Check global variable are still correct.
 > mi_gdb_test "-var-update global_simple" \
 > 	"\\^done,changelist=\\\[\]" \
 > 	"global_simple still alive"
 > 
 > mi_gdb_test "-var-info-type global_simple" \
 > 	"\\^done,type=\"simpleton\"" \
 > 	"type simpleton for valid variable global_simple"
 > 
 > 
 > #
 > # load an other binary
 > # all variables must be invalidated

I guess capital letters at the start and full stops.

 > mi_delete_breakpoints
 > mi_gdb_load ${binfile2}
 > # Check local variable are "invalid"
 > mi_gdb_test "-var-update linteger" \
 > 	"\\^done,changelist=\\\[\{name=\"linteger\",in_scope=\"invalid\"\}\\\]" \
 > 	"linteger not valid anymore due to binary changes"
 > 
 > mi_gdb_test "-var-info-type linteger" \
 > 	"\\^done,type=\"\"" \
 > 	"not type for invalid variable linteger"

 "no type for invalid variable linteger (2)"
 > 
 > # Check global variable are still correct.
 > mi_gdb_test "-var-update global_simple" \
 > 	"\\^done,changelist=\\\[\{name=\"global_simple\",in_scope=\"invalid\"\}\\\]" \
 > 	"global_simple not anymore in scope due to binary changes"
 > 
 > mi_gdb_test "-var-info-type global_simple" \
 > 	"\\^done,type=\"\"" \
 > 	"not type for invalid variable global_simple"
 > 
 
 "no type for invalid variable global_simple"

 > mi_gdb_exit
 > return 0

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-01-31 21:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 12:32 Denis PILAT
2007-01-23 12:45 ` Daniel Jacobowitz
2007-01-23 12:52   ` Vladimir Prus
2007-01-23 14:49     ` Denis PILAT
2007-01-24 21:49       ` Nick Roberts
2007-01-24 22:07         ` Daniel Jacobowitz
2007-01-24 22:08         ` Frédéric Riss
2007-01-24 22:18           ` Nick Roberts
2007-01-24 22:52             ` Frédéric Riss
2007-01-24 23:14               ` Nick Roberts
2007-01-25  2:41             ` Daniel Jacobowitz
2007-01-25 20:50               ` Nick Roberts
2007-01-26  7:25                 ` Denis PILAT
2007-01-23 17:20   ` Denis PILAT
2007-01-25 17:28     ` Denis PILAT
2007-01-25 22:31       ` Nick Roberts
2007-01-25 23:27         ` Daniel Jacobowitz
2007-01-29 12:39           ` Denis PILAT
2007-01-29 22:12             ` Nick Roberts
2007-01-30  8:49               ` Denis PILAT
2007-01-31 19:07               ` Denis PILAT
2007-01-31 21:29                 ` Nick Roberts [this message]
2007-02-01  9:49                   ` Denis PILAT
2007-02-08 16:41                     ` Daniel Jacobowitz
2007-02-08 19:33                       ` Nick Roberts
2007-02-08 19:55                         ` Daniel Jacobowitz
2007-02-09 15:43                         ` Eli Zaretskii
2007-02-12 21:10                           ` Denis PILAT
2007-02-13  0:11                             ` Nick Roberts
2007-02-13  8:26                               ` Denis PILAT
2007-02-20 16:06                             ` Andreas Schwab
2007-02-20 16:17                               ` Denis PILAT

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=17857.2617.164646.935952@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=denis.pilat@st.com \
    --cc=gdb-patches@sourceware.org \
    /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