From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA 2] Debug register support in win32-nat.c
Date: Sun, 13 Jan 2002 10:38:00 -0000 [thread overview]
Message-ID: <20020113183913.GD2647@redhat.com> (raw)
In-Reply-To: <4.2.0.58.20020108102529.021d6ac8@ics.u-strasbg.fr>
On Tue, Jan 08, 2002 at 10:26:12AM +0100, Pierre Muller wrote:
>At 10:20 08/01/2002 , vous avez ?crit:
>> This is a follow up of my first
>>proposal for win32 debug register support
>>(which enables hardware watchpoints,
>>I never tested the hardware breakpoints, as they don't have
>>much advantages over normal breakpoints on i386 processors).
>
>Sorry, I forgot to add the link
>http://sources.redhat.com/ml/gdb-patches/2001-11/msg00537.html
>and all the follow-ups.
I applied this patch but it doesn't seem to build. I get a:
libgdb.a(win32-nat.o): In function `child_mourn_inferior':
/cygnus/src/uberbaum/gdb/win32-nat.c:1398: undefined reference to `_i386_cleanup_dregs'
I assume that this is related to your other patch.
In the meantime, I noticed a couple of things:
- ChangeLog needs to be wrapped to 80 columns.
- ChangeLog wording needs more verbs and more description. For instance:
(debug_registers_changed): Non zero whenever the debug registers where changed and
need to be written to inferior.
You need to mention that this is a new variable:
(debug_registers_changed): New variable. Reflects when debug registers are changed and
need to be written to inferior.
- In do_initial_child_stuff, I'd prefer that you either use sizeof to
derive the size of the dr array for zeroing or use a defined constant,
rather than just a raw "7".
- I'm wondering if your implementation is thread safe? You're storing
debug registers in a global array and copying them into a structure
as needed. Couldn't they just be stored in the per-thread structure?
You could add a debug_registers_used value to the structure, if necessary.
cgf
next prev parent reply other threads:[~2002-01-13 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 1:21 Pierre Muller
2002-01-08 1:26 ` Pierre Muller
2002-01-13 10:38 ` Christopher Faylor [this message]
2002-01-13 15:21 ` muller
2002-01-13 17:58 ` [RFA 2] Debug register support in win32-nat.c (need opinions) Christopher Faylor
2002-01-14 0:15 ` Eli Zaretskii
2002-01-14 0:33 ` Pierre Muller
2002-01-30 9:20 ` Christopher Faylor
2002-02-04 3:04 ` 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=20020113183913.GD2647@redhat.com \
--to=cgf@redhat.com \
--cc=gdb-patches@sources.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