GDB backtrace/run commands

[Zman94]

Hello. I was using this plugin and I noticed it was lacking a couple features that would be nice to have. Namely, it would be nice if there was a run command similar to that when you're inside the gdb debugger. This way, if the program crashes, you could rerun it without running VBGstartGDB again.

Second, it would be nice to be able to run backtrace or where analyze the stack during a run or after a crash without using the rawWrite command.

I hope these features are easy to add. When I free up again, I'll take a look at the code to see if I can add them myself.

[TamaMcGlinn]

At first, I thought that your first suggestion was already implemented, but that was because I have this in my config files:

nnoremap <Leader>gr :VBGrawWrite run<CR>

(where <Leader>g is the same as my g:vebugger_leader, so I don't distinguish between extended and builtin mappings)

The second feature would be quite extensive; a seperate buffer would be opened showing the output of backtrace, where pressing enter on a certain line in there would be equivalent to sending the 'frame' command for that number. It would have to also update whenever a VBG command is issued, with an extra manual command in case someone issues a rawWrite command that changes the backtrace.

I do hope someone builds this.