> Wouldn't this to botch a debugger which supported both backtracing and
> PTRACE_SYSCALL, when stopped in a syscall? We have unwind information
> for the VDSO and it's not going to tell us that the kernel has done
> something clever to the value of %ebp.
The kernel is indeed not supposed to modify any input
registers of syscalls (ok except rcx, but that is unavoidable)
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |