From: Doug Evans <dje@google.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>,
Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] i386/amd64 h/w watchpoints in gdbserver
Date: Thu, 18 Jun 2009 19:04:00 -0000 [thread overview]
Message-ID: <e394668d0906181203t7e043d49n29c2bf563d5f03ea@mail.gmail.com> (raw)
In-Reply-To: <000601c9e988$ff5dc810$fe195830$@u-strasbg.fr>
On Tue, Jun 9, 2009 at 10:04 PM, Pierre Muller<muller@ics.u-strasbg.fr> wrote:
>> > make: *** [check] Error 1
>> >
>> > I got the same results with cygwin gdb itself...
>> >
>> > I am currently investigating the two failures
>> > above and I will come back to this in another email.
>>
>> Hi. For clarification, are these failures regressions, or do the
>> tests still fail without the patch?
>
> Not really, as these two tests are only run
> if the target supports hardware watchpoints.
> This means that current gdbserver from CVS HEAD
> would skip that test.
>
> Anyhow, I think that there are problems with the gdb.threads/watchthreads2.c
> code with cygwin.
> When run directly, this code should write a bunch of thread switches and
> exit,
> but I seems to freeze...
Ping.
next prev parent reply other threads:[~2009-06-18 19:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:19 Doug Evans
2009-05-01 8:10 ` Pierre Muller
2009-05-18 23:11 ` Doug Evans
2009-05-18 23:28 ` Doug Evans
2009-05-19 9:05 ` Pierre Muller
2009-06-02 15:36 ` Doug Evans
2009-06-02 22:47 ` Pierre Muller
2009-06-03 0:18 ` Doug Evans
2009-06-03 16:27 ` Pierre Muller
2009-06-09 3:43 ` Doug Evans
2009-06-10 5:05 ` Pierre Muller
2009-06-18 19:04 ` Doug Evans [this message]
2009-06-20 23:54 ` Pedro Alves
2009-06-23 7:37 ` Doug Evans
2009-06-29 20:45 ` Pedro Alves
2009-06-30 10:32 ` Doug Evans
2009-06-30 10:56 ` Pedro Alves
2009-06-30 15:58 ` Pierre Muller
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=e394668d0906181203t7e043d49n29c2bf563d5f03ea@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--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