Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] i386/amd64 h/w watchpoints in gdbserver
Date: Wed, 03 Jun 2009 00:18:00 -0000	[thread overview]
Message-ID: <e394668d0906021718y35a0c095m9b71846545c7bff0@mail.gmail.com> (raw)
In-Reply-To: <000301c9e3d4$218eac20$64ac0460$@u-strasbg.fr>

On Tue, Jun 2, 2009 at 3:47 PM, Pierre Muller <muller@ics.u-strasbg.fr> wrote:
>> > Do we have an automated testsuite result comparison script that can
>> be
>> > used for gdbserver testing?
>>
>> I just use --target_board=native-gdbserver.exp and compare
>> before/after.
>> ref: http://sourceware.org/gdb/wiki/Native_gdbserver_testing
>>
>> No regressions on amd64 gdbserver, 32-bit and 64-bit.
>
>  Did you try to remove the line saying that
> gdbserver does not support hardware watchpoints,
> does it change anything?

The version I used has:

# Can't do hardware watchpoints, in general.
# But can for i386.
if { [istarget i?86-*-*] || [istarget x86_64-*-* ] } {
    ;# leave unset, testcases check for whether it is defined
} else {
    set_board_info gdb,no_hardware_watchpoints 1
}

Plus while running the testsuite I had this applied:

--- i386-low.c= 2009-06-02 17:11:37.000000000 -0700
+++ i386-low.c  2009-06-02 17:11:52.000000000 -0700
@@ -142,7 +142,7 @@
 #define ALL_DEBUG_REGISTERS(i) for (i = 0; i < DR_NADDR; i++)

 /* Whether or not to print the mirrored debug registers.  */
-static int maint_show_dr = 0;
+static int maint_show_dr = 1;

 /* Types of operations supported by i386_handle_nonaligned_watchpoint.  */
 typedef enum { WP_INSERT, WP_REMOVE, WP_COUNT } i386_wp_op_t;

>
>> >  I can test compilation on cygwin,
>> > but testing can only be done manually...
>>
>> Thanks, can you give this a try?
>
>  I was able to compile without problems
> and test gdb.base/watchpoint.exp
>
> and got 60 PASS (same as gdb itself).

Thanks for running the tests.
How about watchthreads.exp, watchthreads2.exp?


  reply	other threads:[~2009-06-03  0:18 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 [this message]
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
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=e394668d0906021718y35a0c095m9b71846545c7bff0@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