Forum Replies Created
-
Posts
-
Excellent. Thanks a lot. I got it to the point where I can load the elf file, break, single step, and look at variables. However, when I try to set the breakpoint, I get the following type of message:
-break-insert -f /cygdrive/c/svn/NZ04/Firmware/thin_display/stm32fxxx_it.c:190
&”No source file named /cygdrive/c/svn/NZ04/Firmware/thin_display/stm32fxxx_it.c.n”My flow compiles through cygwin, and while the paths seem to work just fine coming from elf into VS, the other way around doesn’t seem to work. I can manually fix the path and enter the break-insert command on the GDB session command line. That works (well, VS GUI is not aware of that breakpoint, but otherwise it is OK).
Is there a fix/workaround that would take care of this issue so I can use F9…?
Perhaps you misunderstood me. It is of great benefit to me to be able to edit/debug from visual studio. I do not want to circumvent VisualGDB and do it all command line. In fact I have a flow that allows me to use openocd/gdb already, and I do use VS as my editor. What I want to do now is to ‘connect’ my make flow to VisualGDB to be able to debug. I would like to use VisualGDB part of your tool, without having to use VisualGNUmake of it, if this makes sense.
Hi ket,
I am trying to have a secondary compilation/testing/debugging flow that does not rely on Visual Studio. That way I could automate some testing on a machine that does not have VS. I could figure out how to compile by looking at VS output window. Now I want to be able to:
– flash the image from command line
– start openocd manually and attach to it with gdb (or visual GDB)
Thanks
