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 00:50:00 -0000 [thread overview]
Message-ID: <20100315005006.GF3045@adacore.com> (raw)
In-Reply-To: <201003141850.49563.pedro@codesourcery.com>
> I've applied the patch below, to address in linux gdbserver the problem
> watchthreads-reorder.exp uncovers, similarly to how it was fixed
> in linux-nat.c.
This is a bit off topic, and even maybe a dream-that-will-never-come-true,
but I've been wondering about sharing the wait loop between GDB and gdbserver.
Sounds like a big job at the very least (in order to extract the code
from GDB for the platform currently supported), but do you think that
it's actually doable / worth the effort? It's just that we're (actually,
mostly you!) are very regularly fixing the same problem twice; once
in GDB, and then once in gdbserver. Given the complexity of this code
on some platforms, it's a real shame.
--
Joel
next prev parent reply other threads:[~2010-03-15 0:50 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 [this message]
2010-03-15 1:22 ` Pedro Alves
2010-03-15 4:45 ` 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=20100315005006.GF3045@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