> You silently overwrite any user ptrace hw breakpoints right? To do it cleanlyThere was work underway on that before (hw_breakpoint). I'm not entirely sure you want to use fancy stuff like that in kgdb. It's nice for kgdb to be as self-contained as possible, so you can debug everything else with it. If you're going to rely on lots of higher-level infrastructure, it could be using kprobes for its software breakpoint handling, too. At any rate, I think it would be good if the hw breakpoint support in kgdb were chopped out into a separate patch. First make kgdb work with no code touching debug registers at all. Then a second patch can add the hw breakpoint support. The latter one can be mulled over or replaced with a hw_breakpoint merge or just put off for a while because it's a big can of worms to multiplex the use of the debug registers. Thanks, Roland --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Eric Sandeen | Re: [RFC] Heads up on sys_fallocate() |
| YOSHIFUJI Hideaki / | request_module: runaway loop modprobe net-pf-1 (is Re: Linux 2.6.21-rc1) |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Ben Greear | Re: MACVLANs really best solution? How about a bridge with multiple bridge virtual... |
| Rafael J. Wysocki | 2.6.29-rc8: Reported regressions from 2.6.28 |
