You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eh, that happens because GDB keeps that information from us Python API users:
>>> python print(gdb.selected_frame().function().name)
Traceback (most recent call last):
File "<string>", line 1, in <module>
AttributeError: 'NoneType' object has no attribute 'name'
Error while executing Python code.
That information is available when the program is compiled with debug symbols (e.g., -g).
It has been historically very hard to figure out the current function information (name and boundaries), there is a huge number of corner cases and the GDB Python API doesn't really help (at least the last time I checked). Any suggestions are more than welcome...
In the Assembly window, I am not seeing the function names. Instead, only "?"s are shown (I marked it red):
When I switch to "layout asm", the function names are displayed correctly:
Is this a bug?
To reproduce, I wrote a simple "Hello World" C program on Kali Linux and compiled it with gcc -o helloworld helloworld.c.
The text was updated successfully, but these errors were encountered: