Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix watchthreads-reorder.exp fails in linux gdbserver
Date: Mon, 15 Mar 2010 04:45:00 -0000	[thread overview]
Message-ID: <20100315044512.GI3045@adacore.com> (raw)
In-Reply-To: <201003150122.00715.pedro@codesourcery.com>

> I believe that at some point this will end up happening, and it
> will be GDBserver's side that will prevail.  It used to be that
> native gdb was much more featureful than gdbserver, but the balance
> is now starting to tip to the other direction.

That, plus the fact that I think that the gdbserver side might be less
entangled - so the code might be easier to pull out and isolate?

In any case, thanks for sharing your thoughts...

-- 
Joel, gdbserver novice ;-)


      reply	other threads:[~2010-03-15  4:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14 18:50 Pedro Alves
2010-03-15  0:50 ` Joel Brobecker
2010-03-15  1:22   ` Pedro Alves
2010-03-15  4:45     ` Joel Brobecker [this message]

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=20100315044512.GI3045@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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