(I checked, the "statics" bool arg in SBFrame::GetVariables refers to static / global variables that are defined in this compilation unit -- the most likely behavior for that argument.)
> On Nov 29, 2014, at 11:41 PM, Jason Molenda <ja...@molenda.com> wrote: > > SBFrame::get_all_variables is a shortcut provided for Python scripts (but is > not available when using the C++ SB API). > > The SBFrame::GetVariables() call I used in my example allows you to specify > whether you want argument variables, static variables (I don't know if this > is function-static or file-static ...), or local variables. I used it in my > example so it would be language-agnostic - valid for either C++ or Python > scripting. > > If you're writing your script in Python (instead of C++), get_all_variables > is fine. There is also get_locals, get_arguments, and get_statics if you > want to pick out some of those variables. > > J > >> On Nov 29, 2014, at 5:19 PM, Jose H <jose.francisco.he...@gmail.com> wrote: >> >> Thank you Jason. >> >> I looked at the online documentation of lldb, that looks like it uses >> doxygen or something, and it is inside the code. >> >> My mind supposed(without thinking) the documentation of this was >> better than the python help so I did not even looked at it. >> >> What is the difference between GetVariables and get_all_variables? >> >> I am a little anxious to have something that minimally work that I >> could publish. >> _______________________________________________ >> lldb-dev mailing list >> lldb-dev@cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > > > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev