Re: reference environment variables from gdb scripts

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 24 Aug 2007 11:26:18 -0700
> From: Sheng-Liang Song <ssl@baymicrosystems.com>
> CC: jan.kratochvil@redhat.com, koling@kchang.net
> 
> Eli Zaretskii wrote:
> > The GDB scripting commands are documented in the GDB user manual.  See
> > the node "Sequences".
> >   
> 
> I am looking for a more detail document.

There isn't one, because I believe everything is described in the user
manual.  If you find something that isn't there, please tell.

> What is the different between "." and "->" operator in gdb script? 
> (Looks like no difference to me. works the same.)
> 
> What operators does gdb 6.6 support?

This is not specific to scripts.  GDB uses operators from the source
language, with C/C++ operators being supported more thoroughly than
those of other languages.  See the node "C Operators" in the manual
for C/C++, and similar nodes for other languages in language-specific
sections under the node "Supported Languages".

In general, anything that is not described in the node "Sequences" and
its sub-nodes is not specific to scripting, but is just a feature of
normal GDB interaction with the user.

> Is a gdb script grammar like this one:
>   http://www.nongnu.org/hcb/

There's no formal description of the script grammar, since the GDB
scripting is just a thin add-on to CLI, the command-line interpreter
built into GDB, and CLI is for human interactions, not for programs.
Humans don't need a formal grammar to interact with programs, only the
format of each command.

> $vec->_M_impl
> STL vector does not have the member var _M_impl.
> gdb) will report: There is no member or method named _M_impl.
> 
> How do I check if $vec has the member _M_impl?

I don't think you can, but I don't consider myself a GDB scripting
guru.  Maybe someone else here will be able to help you.

> I would like to write a script like this:
> 
> if  isMember($vec,_M_impl)
>   //do something
> else
>   //do something else
> end

One way of doing that would be to define within $vec a boolean member
that has the value TRUE only if _M_impl is a valid member, then you
can check for that boolean flag.  Another way is to have a function
isMember inside the $vec class (or a global function in your program)
that would _return_ such a boolean, then you can use what you wrote
above almost verbatim, since GDB can call functions within the
debuggee.

IOW, whatever you want to test must be already present as data in your
program, or else GDB scripting and CLI will not be able to use it in
the `if' clause.

Admittedly, such a scripting is quite limited, which is why there're
plans to add an extension language (Python) to GDB.