Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/Ada] Implement Ada tasking support (take 2)
Date: Fri, 26 Sep 2008 23:24:00 -0000	[thread overview]
Message-ID: <m3od2atrvn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080924174850.GC3607@adacore.com> (Joel Brobecker's message of "Wed\, 24 Sep 2008 10\:48\:50 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel>       However, I think we ought to be consistent about this - I tried
Joel>       searching for other language-specific commands, and indeed,
Joel>       objc-lang defines "info selectors", "info classes", etc.

For "selectors", I don't know; but "info classes" seems like an odd
name for an ObjC-specific command.  Lots of languages have classes.
The language-specific "catch" subcommands are also a bit odd, to me.

Joel>       Tom suggested a different syntax, which is based on using
Joel>       convenience functions in the condition field.
Joel>           break LINESPEC if $current_ada_task() == 5
Joel>       It's an interesting suggestion, and I'm not opposed. I'm just
Joel>       slightly concerned that the performance cost of evaluating
Joel>       a condition expression is higher than just a pure check
Joel>       directly coded in GDB.  It's also different from what is done
Joel>       for threads.

I doubt the overhead is very high, but we can discuss that later if
you want.  It isn't relevant to the current patch :-)

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.)
If this idea applied to task-specific breakpoints then that would be
an argument in favor of putting it in the core, at least IMO.

Tom


  reply	other threads:[~2008-09-26 23:24 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 [this message]
2008-09-26 23:37   ` Pedro Alves
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=m3od2atrvn.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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