Add a test verifying that after the 'watchpoint' command, new values
of x86 debug registers can be read back correctly. The primary purpose
of this test is to catch broken DRn reading and help debugging it.
Details
Diff Detail
Event Timeline
I have a feeling we discussed this already, but I don't remember what was the conclusion.
Was exposing debug registers to the user a conscious choice? Other OSes don't actually do that. Neither does gdb, afaict...
In think that allowing the user to see dr contents is a good idea -- allows him to check what the debugger has done. I'm not convinced about the writing aspect though -- seems like an easy way to confuse the debugger and make it crash...
lldb/test/Shell/Register/x86-db-read.test | ||
---|---|---|
2 | Who sets can-set-dbregs ? |
I agree with this. Hence, I've covered only the reading part. I don't have a strong opinion whether we should ban writes.
lldb/test/Shell/Register/x86-db-read.test | ||
---|---|---|
2 |
lldb/test/Shell/Register/x86-db-read.test | ||
---|---|---|
2 | The feature name is dbregs-set, is it not ? |
lldb/test/Shell/Register/x86-db-read.test | ||
---|---|---|
2 | Indeed it is. Silly me. |
Who sets can-set-dbregs ?