This is the mail archive of the gdb@sourceware.org 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: Python API iterate through the arguments of a frame


On Feb 22, 2012, at 4:06 PM, Tom Tromey wrote:

>>>>>> "Cristian" == Cristian Zamfir <cristian.zamfir@epfl.ch> writes:
> 
> Cristian> Thank you, that would be very useful.  Is there a quick way to see the
> Cristian> names of all available API functions, just in case there are more
> Cristian> undocumented ones, other than looking into the gdb/python/ directory
> Cristian> and infer from the Python bindings (e.g., py-block.c)?
> 
> In addition to the other responses, I'd like to add that we want the
> documentation to be complete and clear; so please file bugs for any
> holes or problems you notice.

Sure, I will. Thanks everyone for the help. 

> 
> Cristian> I can however still retrieve the name and the value of the symbol when
> Cristian> loading a core. Is it possible to also get the type?
> 
> Yes, this information is orthogonal to where the inferior memory comes
> from.
> 
> Cristian> warning: core file may not match specified executable file.
> Cristian> warning: Can't read pathname for load map: Input/output error.
> 
> These could be a problem, but offhand I can't say what is going on.
> 
> I'm surprised about the AttributeError.  I'm not sure how that could
> happen.

It turned out that when I was loading the core I used an older version of gdb (7.3), in which gdb.Symbol did not have the type attribute. Everything works with the latest version. 

Thanks, 
Cristi

> 
> Tom


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