Roland McGrath wrote:
> The tracehook patches are in pretty good shape. I spent a while doing
proper write-ups for each patch's log entry, and fiddling details.
These lay all the groundwork without harming anything. So I am
optimistic that they will not be very controversial upstream (I'd say
/removal
of breakpoints and for single stepping over an out of line copy of the
instruction.
Roland,
Patch attached in the above mail implements breakpoint assistance for
utrace clients, Could you please review my patch and let me know your
views on this.
Thanks
Srinivasa DS
Hi Roland
Thanks for rebasing utrace patch on 2.6.25-rc6. On applying your patch, I
executed ptrace tests on my ppc system. I found 4 failures and most of the
failures are due to ptrace (PTRACE_SINGLESTEP, child, NULL, NULL) call.
This call fails with -ENOSYS.
PASS: ptrace-on-job-control-stop
patches, it didn't
get applied when I build the kernel using "rpmbuild" command.
So could you please point us to latest utrace patches.
Thanks
Srinivasa DS
Srinivasa Ds wrote:
Hi
I was executing Alexey's testcase cited in
(http://marc.info/?l=linux-kernel&m=117128445312243&w=2) to test the utrace and
system crashed on pressing ctr+c.
This leads me to suspect a possible issue with the usage of RCU in utrace.
Please let
Hi
I was executing Alexey's testcase cited in
(http://marc.info/?l=linux-kernel&m=117128445312243&w=2) to test the utrace and
system crashed on pressing ctr+c.
Environment: 2.6.23-rc7, ppc64.
6:mon> e
cpu 0x6: Vector: 300 (Data Access) at [c0002510b650]
pc: c038b0f8: ._spin