<WeaselSoup>
"Do not use GDB commands continue, step or next as they synchronize GDB with your target and GDB would require stopping the target to get the prompt back. "
<Haohmaru>
"Do not use GDB commands continue, step or next as they ..." <- this?
<WeaselSoup>
yeah
<Haohmaru>
but that's in a particular context afaict
<Haohmaru>
those commands are generally legit and they work
<Haohmaru>
it's maybe like "if the gun is pointed at your head - don't use the SHOOT command."
<PaulFertser>
WeaselSoup: yes, it's in the section "20.5 Using GDB as a non-intrusive memory inspector" :)
<Haohmaru>
doesn't mean it won't work
<WeaselSoup>
Also this
<WeaselSoup>
"If your project controls more than a blinking LED, let’s say a heavy industrial robot or an experimental nuclear reactor, stopping the controlling process just because you want to attach GDB is not a good option. "
<PaulFertser>
WeaselSoup: right so?
<WeaselSoup>
As I'm using gdb+openocd on a phone
<WeaselSoup>
I was guessing that hbreak+continue would cause some problems
<Haohmaru>
when you break (pause) a running target, you... uhm... disrupt its normal operation
<Haohmaru>
that is expected and unavoidable
<WeaselSoup>
sure
<WeaselSoup>
So except the configuations options suggested on the page I might just try and see ?
<Haohmaru>
so if it's some MCU that controlls the cooling of a nuclear power plant type of thing, you probably shouldn't be doing things without deeply understanding the consequences
<WeaselSoup>
yeah
<Haohmaru>
if you see me in a nuclear power plant with a debugger - run, run fast!
<Haohmaru>
WeaselSoup, have you debugged a computer program?
<Haohmaru>
like, a console app
<WeaselSoup>
yes
<Haohmaru>
well then, debugging with gdb thru openocd is very similar
<Haohmaru>
break and continue generally work
<WeaselSoup>
ok
<WeaselSoup>
I tried continue + Ctrl-C to see
<WeaselSoup>
it didn't go well, but that might be a limitation of the target / implementation
<PaulFertser>
WeaselSoup: you normally do not need any special options for GDB to work with OpenOCD.
<PaulFertser>
And the manual doesn't really suggest any options for general usecase.
eliasph88 has joined #openocd
<eliasph88>
Hi, I am currently trying to use the "adapter driver xlnx_pcie_xvc" option, and got stuck. I fist have some permission issues to the PCIe device configurations files but now that part is fine. Nevertheless have some other. unfortunately, the error code I am getting is always the same : "Debug: 37 1 command.c:528 exec_command(): Command 'init'