Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.
We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.
Thank you for your understanding.
Greetings,
Im experiencing strange behaviour of my DS-5 debugger when I try to #include <tuple>. After including this header, my debugger gets messy (i.e Variables window is not showing any local scope data, program is not running from symbol main stucking at _ZL20__gthread_key_deletei symbol). Do i have to add something while compiling to support this feature ? To clarify, program and all tuple stuff compiles and works as expected - only debugger seems to get broken.
Im linking with --specs=nosys.specs -nostartfiles -T ${CMAKE_SOURCE_DIR}/linker/script.ld
Thanks for reporting. I don't think compiler need any special feature to support including of a standard header file. You migh want to try if gdb has the same issue with your case?
Hi, What do you mean by that ? :D I think i solved this issue by forcing -gstrict-dwarf (after I've found this thread community.arm.com/.../ds-5-fvp-debugger-always-shows-failed-to-load-symbols-for-hello-world-axf). Is there any official statement about any debug related GCC flag which should be used while debugging in DS-5 ?