[zzattack]

You seem to be correct, I get much different results with older j-link releases to a point where debugging is somewhat functional.
The issue I run into with those is setting breakpoints while a program is running:

“Failed to create a breakpoint: Cannot execute this command while the target is running. Use the “interrupt” command to stop the target and then try again.”

Manually adding a ‘interrupt’ in the GDB window does the trick but it feels as if VisualGDB should be able to take care of this.

Hitting ‘break all’ and then setting a breakpoint doesn’t work either. Worse yet, resuming doesn’t work then either:

-exec-continue
Cannot execute this command while the selected thread is running.
-stack-list-frames --thread 1
Selected thread is running.
-stack-list-frames --thread 1 0 0
Selected thread is running.
-data-evaluate-expression --thread 1 "\$pc"
Selected thread is running.
-stack-list-frames --thread 1
Selected thread is running.
-stack-list-frames --thread 1 0 0
Selected thread is running.
-data-evaluate-expression --thread 1 "\$pc"
Selected thread is running.

I can’t tell whether this is VisualGDB or J-Link related and/or whether (soft-) remedies are available.

[zzattack]

Excellent, I can confirm this addresses the issue. Thanks for the fast resolution!

[zzattack]

http://pastebin.com/N6DBBmQS

 

Here’s the log.

[zzattack]

If I do so, I get a message “Command aborted.” in the GDB session window. When I then try to remove the extra breakpoints, I get into the same behavior where it hangs.

This is my first project with VisualGDB, haven’t tested it on another microcontroller before.

• This reply was modified 8 years ago by zzattack.

[Author]

Posts