This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)
- From: "Philippe Waroquiers" <philippe dot waroquiers at skynet dot be>
- To: "Pedro Alves" <pedro at codesourcery dot com>, <gdb-patches at sourceware dot org>
- Cc: "Yao Qi" <yao at codesourcery dot com>, "Tom Tromey" <tromey at redhat dot com>
- Date: Sun, 5 Jun 2011 22:54:49 +0200
- Subject: Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)
- References: <CDA9C6B129F5458D9301BA5289052C97@soleil> <201105311830.59328.pedro@codesourcery.com> <1A6A06B5CD4346FEB0EAE0998527F07D@soleil> <201106011615.03444.pedro@codesourcery.com>
Note that one other thing that I find confusing in the current behaviour
is that if you have a certain set of hw watchpoints that were accepted
and you add a new one, you might obtain an error back referencing
an "old" accepted watchpoint.
I think it would be better if the watchpoints would always be re-inserted
by gdb in the same order.
I suppose that if we made insert_breakpoint_locations
walk breakpoints by increasing number instead of walking by
breakpoint locations, it'd be good enough.
Yes, I think this is avoiding the strange behaviour of having
an error on a previously accepted watchpoint.
If breakpoint always-inserted is on, then I thinkl the error will appear immediately,
which is also ok.
Thanks for the patch to fix the 'busy' debug register on x86, I should be able
to evaluate it end of this week.
Philippe