This is the mail archive of the gdb-prs@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]

[Bug gdb/20143] ARM (rPi2): Debugging "top" fails: /build/gdb-nrlhe3/gdb-7.7.1+dfsg/gdb/frame.c:472: internal-error: get_frame_id: Assertion `fi->this_id.p' failed


https://sourceware.org/bugzilla/show_bug.cgi?id=20143

--- Comment #3 from Arnout <arre_diels at hotmail dot com> ---
Well in fact there is still a bug, even in the last version.
The stepi's still work, but if I try to check the registers at this point,
things go bad again:

GNU gdb (GDB) 7.11.50.20160525-git
...

0x76eb8d58 in select () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) stepi
0x76eb8d5c in select () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) stepi
0x76eb8d60 in select () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) stepi
0x0000ccdc in ?? ()
(gdb) bt
#-1 0x0000ccdc in ?? ()
Backtrace stopped: Cannot access memory at address 0xe
(gdb) bt
#-1 0x0000ccdc in ?? ()
Backtrace stopped: Cannot access memory at address 0xe
(gdb) info reg
findvar.c:291: internal-error: value* value_of_register_lazy(frame_info*, int):
Assertion `frame_id_p (get_frame_id (frame))' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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