Forum Replies Created
-
Posts
-
This was set-up and working Fine for debugging for months. VGDB updated the toolchain and now it does not work. Going back to old toolchain does not work.
Reinstalling VGDB, toolchain and segger tools. Does VGDB test all the with all the toolchains before releasing?
We are using Nordic nRF51822 and have a VS2015 project used to build our app (connect with Jlink, latest segger tools installed 6.16d). Its worked fine -until yesterday. Pulled project out of GIT, opened project and VGDB updated the toolchain to latest (Tried to revert to previous version of tools, but still get same error message. ). Now we get following error message when trying to load code after build.
“\tEntry point: 0x1337c\n”
~”\t0x00003800 – 0x00023030 is .text\n”
~”\t0x00023030 – 0x00023038 is .ARM.exidx\n”
~”\t0x20000000 – 0x2000034c is .data\n”
~”\t0x2000034c – 0x2000036c is .bootloaderSettings\n”
~”\t0x20000370 – 0x20003ce8 is .bss\n”
^done
-data-evaluate-expression “&_estack”
^error,msg=”No symbol \”_estack\” in current context.”
-data-evaluate-expression “&__StackLimit”
^done,value=”0x20004000 <error: Cannot access memory at address 0x20004000>”
-var-create – * “*((void **)0x20003ffc)”
^done,name=”var1″,numchild=”0″,value=””,type=”void *”,has_more=”0″
-var-evaluate-expression “var1″
^done,value=””
-exec-continue
^error,msg=”The program is not being run.”I actually tried Visual Watch prior to Live variables. Not able to add any variables to Visual Watch – with either new or production VisualGDB.
Correct. So add a variable to live variable display, say int Foo[100], run program and hit break point. Examine Foo and export contents (100 integers) to csv file.
Thanks!
A couple comments.
1) For small embedded systems, there may Not be another good way to get a snapshot of a variable out of a device.
2) When collecting debug information for Other people to see – it is important to be able to save a snapshot of a large variable to a CSV text file. Often this data gets input to matlab or other for additional processing and perhaps complex graph/charting.
This is a very different Use case then debugging for code problems/issues.
I tried the new VisualGDB build. The ‘Save to CSV’ file now saves a file when a variable is selected in the Live Variable display. Unfortunately the file it save is empty.
A few other notes.
1) Each variable selected seems to open a new file. So for instance if you have a buffer FooBuff (from Live Variables display) that is 100 elements long, selecting all 100 elements in FooBuff would create 100 files. I just want to select FooBuff and have it save the whole vector to one file.
2) This is a nit – but it takes 20-30 seconds to start Visual Studio when ‘large’ vectors (100 elements) are added to the Live Variables display. It appears that much of this time is because the vectors are expanded in the display (e.g. – all the elements of FooBuff would be expanded an shown after VS starts.
3) Currently there does not seem to be ANY way to save debugger variables to disk. So you can either copy manually from the debugger or fire-up your favorite OCR program ;).
