This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: adjust watchpoint testing


Wu Zhou wrote:
Nathan,

I had similar concerns about these watchpoint tests with you. However, I'd like to propose a somewhat different solution.

This target-dependent feature might incur confusion some where. One may have difficulty in knowing for sure what this case is trying to test: s/w watchpoint, or h/w watchpoint, or both? If there are errors reported, what type of watchpoint trigger that? To track into the root cause, which code to look at?

To clarify the situation, I propose to let recurse.exp based on totally on software simulated watchpoint. This can be done easily, by using "set can-use-hardware-watchpoint 0".

Thanks for your comments. Over the weekend, I had a thought that the problem is the remote stub not telling gdb how many watchpoints it can support. I think this is a thing for qPacketInfo to deal with, and I can talk to Dan about that.


nathan
--
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]