Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marius Groeger <mag@sysgo.de>
To: gdb-patches@sources.redhat.com
Cc: Daniel Junglas <dju@sysgo.de>, Wolfgang Denk <wd@denx.de>
Subject: Multi-Threaded Extensions for GdbServer
Date: Wed, 22 May 2002 02:14:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.40.0205221041320.480-101000@mag.devdep.sysgo.de> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 982 bytes --]

Hi all,

several people asked me to post this to the wider audience of gdb
developers. AFAIK there are several approaches for extending the
gdbserver to be able to debug remote programs that use threads. The
attached patch does this. The main advantage of it is that it doesn't
require libthread_db or symbol information on the target. We need
this for debugging of embedded targets with limited resources.
The main downside of the patch is that it's for some pretty ancient
5.0 snapshot (20010427). It also contains a small number of general
fixes which are not related to MT debugging.

Regards,
Marius

-----------------------------------------------------------------------------
Marius Groeger           SYSGO Real-Time Solutions GmbH     mgroeger@sysgo.de
Software Engineering     Embedded and Real-Time Software    www.sysgo.de
Voice: +49-6136-9948-0   Am Pfaffenstein 14                 www.osek.de
FAX:   +49-6136-9948-10  55270 Klein-Winternheim, Germany   www.elinos.com

[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 39711 bytes --]

             reply	other threads:[~2002-05-22  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22  2:14 Marius Groeger [this message]
2002-05-25 23:13 ` Daniel Jacobowitz
2002-05-27  2:17   ` Marius Groeger
2002-05-28 18:05   ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.40.0205221041320.480-101000@mag.devdep.sysgo.de \
    --to=mag@sysgo.de \
    --cc=dju@sysgo.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=wd@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox