From: Valery Khromov <valery.khromov@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR gdb/12953: No hardware watchpoints on FreeBSD amd64
Date: Tue, 20 Dec 2011 18:30:00 -0000 [thread overview]
Message-ID: <7B4892D2-0598-40F0-8585-AF48FA6A5123@gmail.com> (raw)
In-Reply-To: <m3k45rmhix.fsf@fleche.redhat.com>
On 20.12.2011, at 17:42, Tom Tromey wrote:
>>>>>> "Valery" == Valery Khromov <valery.khromov@gmail.com> writes:
>
> Valery> This patch provides hardware breakpoint/watchpoint support for
> Valery> FreeBSD/AMD64. Most of the code is borrowed from the i386
> Valery> implementation.
>
> I'm sorry nobody has replied to this yet.
>
> I'm not really the right person to review it.
>
> Do you have copyright assignment paperwork filed with the FSF?
No, I don't.
How can I do it?
--
WBR,
Valery Khromov
next prev parent reply other threads:[~2011-12-20 17:56 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 [this message]
2011-12-21 6:45 ` Joel Brobecker
2011-12-20 15:04 ` Mark Kettenis
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=7B4892D2-0598-40F0-8585-AF48FA6A5123@gmail.com \
--to=valery.khromov@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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