Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org,  tromey@redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA/Ada] Implement Ada tasking support (take 2)
Date: Fri, 26 Sep 2008 23:37:00 -0000	[thread overview]
Message-ID: <200809270036.56455.pedro@codesourcery.com> (raw)
In-Reply-To: <m3od2atrvn.fsf@fleche.redhat.com>

On Saturday 27 September 2008 00:22:04, Tom Tromey wrote:
> I thought I heard an argument to the effect that thread-specificity
> could be more efficiently implemented at a low level, at least in
> theory, on some platforms.  (I don't know.  And that is mighty vague.)

That is usually brought about in the remote target context.  Currently,
a thread specific breakpoint is implemented by letting any thread hit
it, and then having GDB's inferior control side check if it was the
thread the user specified --- if so, stop; or, if some other thread hit
it --- then resume immediatelly.  If the thread associated with
the breakpoint is communicated to the lower target layers, we can minimize
this overhead by having the target itself filter those uninteresting
breakpoint hits.  This extra overhead is of course more visible when
you have a serial communication protocol in the middle.  Currently,
the remote protocol has no support for thread-specific breakpoints,
though, so usually talking about this ends up with a 'IWBN'.

-- 
Pedro Alves


  reply	other threads:[~2008-09-26 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 17:50 Joel Brobecker
2008-09-26 23:24 ` Tom Tromey
2008-09-26 23:37   ` Pedro Alves [this message]
2008-10-07  4:24 ` Joel Brobecker
2008-10-22 19:59 ` Joel Brobecker
2008-10-22 22:37   ` Jan Kratochvil
2008-10-23  0:49     ` Joel Brobecker
2008-10-23  8:10       ` Jan Kratochvil
2008-10-23 14:48         ` Joel Brobecker

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=200809270036.56455.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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