RMT ERROR : failed to get remote thread list

RMT ERROR : failed to get remote thread list

[Peter Skvarka]

I use arm-elf-insight version 6.6 and after success connect into OpenOCD
with JTAG,
I am trying to issue in gdb console:
"info threads"
after it there is displayed two dialog boxes:
"RMT ERROR : failed to get remote thread list"
and
"couldn't restore frame in current thread, at frame 0"

What does it mean this error ? How can I correct it ?

Thanks,
Peter

Re: RMT ERROR : failed to get remote thread list

[Daniel Jacobowitz]

On Wed, Sep 19, 2007 at 02:46:00PM +0200, Peter Skvarka wrote:
> I use arm-elf-insight version 6.6 and after success connect into OpenOCD
> with JTAG,
> I am trying to issue in gdb console:
> "info threads"

If you are using a JTAG device to talk to your target, it probably
does not support threads.  However, it looks like it is not correctly
reporting that it does not support threads.

> after it there is displayed two dialog boxes:
> "RMT ERROR : failed to get remote thread list"
> and
> "couldn't restore frame in current thread, at frame 0"
> 
> What does it mean this error ? How can I correct it ?

Compare the remote protocol manual with what OpenOCD is doing, and
change OpenOCD's behavior to correctly report unsupported commands.

-- 
Daniel Jacobowitz
CodeSourcery

RE: RMT ERROR : failed to get remote thread list

[Peter Skvarka]

I need to run "info threads" dgb command to see address of text section for
some running executable.
Does not exist some other way how to determine address of text section of
loaded executable ?
"info threads" is in gdb only way I know, but I dont know gdb very good. 

Thanks !
Peter

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Wednesday, September 19, 2007 3:20 PM
To: Peter Skvarka
Cc: gdb@sourceware.org
Subject: Re: RMT ERROR : failed to get remote thread list

On Wed, Sep 19, 2007 at 02:46:00PM +0200, Peter Skvarka wrote:
> I use arm-elf-insight version 6.6 and after success connect into 
> OpenOCD with JTAG, I am trying to issue in gdb console:
> "info threads"

If you are using a JTAG device to talk to your target, it probably does not
support threads.  However, it looks like it is not correctly reporting that
it does not support threads.

> after it there is displayed two dialog boxes:
> "RMT ERROR : failed to get remote thread list"
> and
> "couldn't restore frame in current thread, at frame 0"
> 
> What does it mean this error ? How can I correct it ?

Compare the remote protocol manual with what OpenOCD is doing, and change
OpenOCD's behavior to correctly report unsupported commands.

--
Daniel Jacobowitz
CodeSourcery

Re: RMT ERROR : failed to get remote thread list

[Daniel Jacobowitz]

On Wed, Sep 19, 2007 at 04:22:59PM +0200, Peter Skvarka wrote:
> I need to run "info threads" dgb command to see address of text section for
> some running executable.
> Does not exist some other way how to determine address of text section of
> loaded executable ?
> "info threads" is in gdb only way I know, but I dont know gdb very good. 

Again, you can not debug Linux userspace programs by using OpenOCD and
JTAG.  You need to use the gdbserver program.  When you connect to
your board using OpenOCD, you can only debug the kernel and you won't
see a threads list.

-- 
Daniel Jacobowitz
CodeSourcery

RE: RMT ERROR : failed to get remote thread list

[Peter Skvarka]

If I understand good, I must to compile gdbserver for my target ARM9,
and place it and start it on my embedded board ?
Does exist some tutorial for this ?

Peter 


-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Wednesday, September 19, 2007 4:28 PM
To: Peter Skvarka
Cc: gdb@sourceware.org
Subject: Re: RMT ERROR : failed to get remote thread list

On Wed, Sep 19, 2007 at 04:22:59PM +0200, Peter Skvarka wrote:
> I need to run "info threads" dgb command to see address of text 
> section for some running executable.
> Does not exist some other way how to determine address of text section 
> of loaded executable ?
> "info threads" is in gdb only way I know, but I dont know gdb very good. 

Again, you can not debug Linux userspace programs by using OpenOCD and JTAG.
You need to use the gdbserver program.  When you connect to your board using
OpenOCD, you can only debug the kernel and you won't see a threads list.

--
Daniel Jacobowitz
CodeSourcery