-breakpoint register (like older PPC64 with 1 IABR) in the
system. If one process/thread consumes it, then all other contenders (from
both kernel and user-space) are prevented from acquiring it.
Also to mention the existence of processors with no support for
instruction breakpoints.
Thanks,
K.Prasad
().
Thanks,
K.Prasad
prasadkr]#
Am I missing something here?
Thanks,
K.Prasad
On Fri, Dec 11, 2009 at 04:59:44PM +0100, Oleg Nesterov wrote:
On 12/11, K.Prasad wrote:
Watchpoints (using DABR) through GDB can fail for many reasonsthey
must ideally be set after the program has started execution - to enable
GDB know the size of the variable...else they would resort
-stepping to trap access to the target variable.
Cai,
Where can one find the relevant piece of testcase?
Thanks,
K.Prasad
On Tue, Jul 01, 2008 at 03:28:04PM -0400, Chris Moller wrote:
K.Prasad wrote:
Hi All,
Sorry if I have missed out something I need to know before I
respond to this email. But the trace infrastructure (lib/trace.c)
already provides such a facility which more features such as per-cpu
