This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Fix Cygwin problem with banned variables

>   This generates multiple calls to 'trace variable ' and only one call
>   to 'trace remove variable '.

The TCL documentation is not directly explicit about that, but
some experimentation shows that this is indeed a problem. And
rereading the docuemntation with that in mind, the duplicate traces
are probably treated as distinct traces.  Thus, when doing only one
remove for the trace, we're still left with at least one trace.

> 2010-06-19  Pierre Muller  <>
> 	* lib/gdb.exp (banned_variables_traced): New global variable.
> 	(gdb_init, gdb_finish): Use new variable to avoid multiple
> 	tracing.
> 	(gdb_init): Use `trace add variable ' instead of obsolete
> 	`trace variable '.

Just one detail, but otherwise OK.

> @@ -2519,6 +2519,7 @@ if ![info exists gdb_test_timeout] {
>  # We try to prevent their use by monitoring write accesses and raising
>  # an error when that happens.
>  set banned_variables { bug_id prms_id }
> +set banned_variables_traced 0

Please add a comment explaining what this global is used for and
why it is necessary.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]