After some research I found that OpenOCD can't send current thread
value. It's GDB that ask for it, and only one time !
We have to change something in GDB, so I opened a bug report in bugzilla
: http://sourceware.org/bugzilla/show_bug.cgi?id=15643
If someone can help don't hesitate to use bugzilla
The problem is that GDB ask for current thread id before OpenOCD compute it.
If we block it GDB won't let you connect to OpenOCD, IMO we have to let
it like that and try to change the current thread when we upload .elf file.
Vivien
On 17/06/2013 10:45, Vivien Giraud wrote:
> Hi everyone,
>
> I
Hi everyone,
I found where all my problem come from !
Each time I want to print the thread list in GDB I'v got a error because
openOCD try to read at 0x0.
After lots of reading and observations I found that GDB allways say that
the last thread is the current one (using '*').
So, using traces, I fo
