From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: valery.khromov@gmail.com
Cc: gdb-patches@sourceware.org, valery.khromov@gmail.com
Subject: Re: [PATCH] Fix PR gdb/12953: No hardware watchpoints on FreeBSD amd64
Date: Tue, 20 Dec 2011 15:04:00 -0000 [thread overview]
Message-ID: <201112201503.pBKF390e027750@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1323132864-14029-1-git-send-email-valery.khromov@gmail.com> (message from Valery Khromov on Tue, 6 Dec 2011 04:54:24 +0400)
> From: Valery Khromov <valery.khromov@gmail.com>
> Date: Tue, 6 Dec 2011 04:54:24 +0400
>
> This patch provides hardware breakpoint/watchpoint support for
> FreeBSD/AMD64. Most of the code is borrowed from the i386 implementation.
I fear that since the recent changes that Pedro made, the code needs
to be resycnhed with the i386 version :(. Can you do that?
While you're at it, here are a few comments.
> gdb/ChangeLog:
> 2011-12-05 Valery Khromov <valery.khromov@gmail.com>
>
> PR gdb/12953
> * Makefile.in (HFILES_NO_SRCDIR): Add amd64bsd-nat.h.
> * amd64bsd-nat.c: Add support for debug registers (adapted from
> i386bsd-nat.c).
> [HAVE_PT_GETDBREGS] (DBREG_DRX): Define if not already defined.
> [HAVE_PT_GETDBREGS] (amd64bsd_dr_set, amd64bsd_dr_set_control,
> amd64bsd_dr_set_addr, amd64bsd_dr_reset_addr, amd64bsd_dr_get_status):
> New functions.
> * amd64bsd-nat.h: New file (adapted from i386bsd-nat.h).
> * amd64fbsd-nat.c: Include "amd64bsd-nat.h", "i386-nat.h".
> [HAVE_PT_GETDBREGS] (_initialize_amd64fbsd_nat): Add hardware
> watchpoints initialization.
> * config/i386/fbsd64.mh (NATDEPFILES): Add i386-nat.o.
>
> --- a/gdb/amd64bsd-nat.c
> +++ b/gdb/amd64bsd-nat.c
> @@ -126,3 +126,80 @@ amd64bsd_target (void)
> t->to_store_registers = amd64bsd_store_inferior_registers;
> return t;
> }
> +\f
> +
> +/* Support for debug registers. */
> +
> +#ifdef HAVE_PT_GETDBREGS
> +
> +/* Not all versions of FreeBSD/amd64 that support the debug registers
> + have this macro. */
> +#ifndef DBREG_DRX
> +#define DBREG_DRX(d, x) ((&d->dr0)[x])
> +#endif
That bit can go. FreeBSD/amd64 has always had the DBREG_DRX macro, at
least ever since support for debug registers was added.
next prev parent reply other threads:[~2011-12-20 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 2:41 Valery Khromov
2011-12-20 14:52 ` Tom Tromey
2011-12-20 18:30 ` Valery Khromov
2011-12-21 6:45 ` Joel Brobecker
2011-12-20 15:04 ` Mark Kettenis [this message]
2011-12-20 16:12 ` Pedro Alves
2011-12-20 17:52 ` Valery Khromov
2011-12-20 17:53 ` [PATCH 1/2] FreeBSD/amd64: Updates for the recent changes that Pedro Alves made Valery Khromov
2011-12-20 17:56 ` [PATCH 2/2] FreeBSD: Removed definition of DBREG_DRX macro because it is already in FreeBSD Valery Khromov
2011-12-20 19:44 ` [PATCH] Fix PR gdb/12953: No hardware watchpoints on FreeBSD amd64 Mark Kettenis
2011-12-20 20:38 ` [PATCH v2] " Valery Khromov
2012-01-31 17:50 ` Valery Khromov
2012-02-01 20:27 ` Tom Tromey
2012-02-02 9:03 ` Valery Khromov
2012-02-11 18:51 ` Mark Kettenis
2012-02-11 21:03 ` Valery Khromov
2012-02-09 16:10 ` Pedro Alves
2011-12-20 16:05 ` [PATCH] " Pedro Alves
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=201112201503.pBKF390e027750@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=valery.khromov@gmail.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