This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What does gdb stub need for thread aware debugging on embedded system?

From: Daniel Jacobowitz <drow at false dot org>
To: Michael Snyder <msnyder at specifix dot com>
Cc: John Carter <john dot carter at tait dot co dot nz>, gdb at sourceware dot org
Date: Sun, 15 Jun 2008 21:44:01 -0400
Subject: Re: What does gdb stub need for thread aware debugging on embedded system?
References: <alpine.DEB.1.00.0806161145460.17082@parore.tait.co.nz> <1213575599.3601.898.camel@localhost.localdomain>

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

References:
- What does gdb stub need for thread aware debugging on embedded system?
  - From: John Carter
- Re: What does gdb stub need for thread aware debugging on embedded system?
  - From: Michael Snyder

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]