* What does gdb stub need for thread aware debugging on embedded system?
@ 2008-06-16 0:10 John Carter
2008-06-16 0:20 ` Michael Snyder
0 siblings, 1 reply; 3+ messages in thread
From: John Carter @ 2008-06-16 0:10 UTC (permalink / raw)
To: gdb
I'm looking to get thread aware debugging running on our "sparc-alike"
Leon II processor.
Unlike the usual sparc stub, I cannot get thread information from
Solaris as we're not running solaris on this device.
If I understand things correctly, getting gdb working should just be a
matter of tying gdb/sparc-stub.c to our serial ports by defining
extern void putDebugChar(); /* write a single character */
extern int getDebugChar(); /* read and return a single char */
Grepping through that code the word "thread" doesn't occur.
What I'm missing is how does gdb get information about threads from
the devices OS to gdb running on the desktop.
Any pointers to the right bit of documentation / code would be most
welcome.
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : john.carter@tait.co.nz
New Zealand
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: What does gdb stub need for thread aware debugging on embedded system?
2008-06-16 0:10 What does gdb stub need for thread aware debugging on embedded system? John Carter
@ 2008-06-16 0:20 ` Michael Snyder
2008-06-16 1:44 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Michael Snyder @ 2008-06-16 0:20 UTC (permalink / raw)
To: John Carter; +Cc: gdb
On Mon, 2008-06-16 at 12:09 +1200, John Carter wrote:
> I'm looking to get thread aware debugging running on our "sparc-alike"
> Leon II processor.
>
> Unlike the usual sparc stub, I cannot get thread information from
> Solaris as we're not running solaris on this device.
>
> If I understand things correctly, getting gdb working should just be a
> matter of tying gdb/sparc-stub.c to our serial ports by defining
> extern void putDebugChar(); /* write a single character */
> extern int getDebugChar(); /* read and return a single char */
>
> Grepping through that code the word "thread" doesn't occur.
>
> What I'm missing is how does gdb get information about threads from
> the devices OS to gdb running on the desktop.
>
> Any pointers to the right bit of documentation / code would be most
> welcome.
At the time that that code was written, threads were very far from
the minds of people who wrote remote gdb stubs!
Look at gdbserver -- it has support for threads.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: What does gdb stub need for thread aware debugging on embedded system?
2008-06-16 0:20 ` Michael Snyder
@ 2008-06-16 1:44 ` Daniel Jacobowitz
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2008-06-16 1:44 UTC (permalink / raw)
To: Michael Snyder; +Cc: John Carter, gdb
On Sun, Jun 15, 2008 at 05:19:59PM -0700, Michael Snyder wrote:
> At the time that that code was written, threads were very far from
> the minds of people who wrote remote gdb stubs!
Yeah. While sparc-stub.c is a valid example, keep in mind that it is
a very old one. There's been a tremendous amount of change in the
remote protocol since then, including in the threads area (see
e.g. the description of vCont in the remote protocol documentation,
which is in the GDB manual).
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-06-16 1:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-06-16 0:10 What does gdb stub need for thread aware debugging on embedded system? John Carter
2008-06-16 0:20 ` Michael Snyder
2008-06-16 1:44 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox