06-03-2014 07:23 AM
I'm on a ZedBoard (Zynq7020), got some OO design in C++, and GDB won't stop crashing (mostly when stepping / running into breakpoints).
Downloading works fine, but at some point, after stepping into and out of some functions/methods, GDB delivers following (or similar) error message(s):
15:40:57 ERROR : Unexpected error while launching program.
java.lang.RuntimeException: Target request failed: Cannot access memory at address 0x10e364.
...and Windows (7, 64 bit) says "arm-xilinx-eabi-gdb.exe has stopped working...".
Also, before crashing, it happens very often that I can't access Expressions and view my variable contents in the Eclipse/SDK GUI. It might be that these two bugs have something to do with each other. Both are really annoying, I can say that.
I tried removing -std=c++11 flag, no change. Also, I have -O0 and -g3 activated.
Enough stack and heap size should be assigned (a few megabytes each, if GDB even needs it, I don't know...).
I tried upgrading from SDK 2013.4 to 2014.1, no change at all.
Sometimes, when changing smaller code segments, I can watch the contents of my Variables and Expressions when stepping, and GDB crashes at a later time, or earlier, or not. I could not find a pattern there...
Thanks in advance and best regards,
06-03-2014 10:18 AM
small update: i managed to get a different error message in the Console window of the SDK:
/scratch/janisjo/build3/2013.11-xilinx-eabi-release/obj/gdb-src-2013.11-46-arm-xilinx-eabi-i686-mingw32/gdb/infrun.c:1965: internal-error: resume: Assertion `pc_in_thread_step_range (pc, tp)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
this is looking highly buggy, along with a thousand other things in the xilinx toolchain... i'm soriously thinking about stepping away from it, it's only been troubling so far.
06-04-2014 04:49 AM
Would that be possible to use System Debugger?
There are a few known issues with the SDK GDB debugger as mentioned in the below link