On Sat, Jan 23, 2010 at 2:22 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
This is why when somebody brought up you could do a seccomp-like thing on
top of utrace that my reaction was and is just totally negative. It shows
all the wrong kinds of tying things together.
The killer app for this will be the ability to delete thousands of
lines of code from GDB, strace, and all the various other tools that
have to painfully work around the major interface gotchas of ptrace(),
while at the same time making their handling of complex processes much
more robust.
* Kyle Moffett k...@moffetthome.net wrote:
On Fri, Jan 22, 2010 at 19:22, Linus Torvalds
torva...@linux-foundation.org wrote:
There are cases where we really _want_ to have common code. We want to
have a common VFS interface because we want to show _one_ interface to
user space across a
Hi -
mingo wrote:
[...]
Now how do we get from here to a moderately portable API for interrogating,
controlling, and intercepting process state? Essentially it would need to
support all of the things that a powerful debugger would want to do,
including modifying registers and memory,
Hi -
On Sat, Jan 23, 2010 at 11:01:21AM +, Alan Cox wrote:
[...]
What I don't understand is why [libgdb?] doesn't solve 99% of your problem.
ptrace is not perfect but most of the real ptrace limitations actually
come about because either the CPU can't do something or because the
Em Sat, Jan 23, 2010 at 11:01:21AM +, Alan Cox escreveu:
Years ago (and it really must be years ago because this was about the
time I started hacking on Linux stuff !) there was a proposal to extract
and sanitize the arch specific stuff in binutils and in gdb etc into
sensible libraries
On Sat, Jan 23, 2010 at 06:47:29AM -0500, Frank Ch. Eigler wrote:
What utrace does is that it provides an opaque set of APIs for
unspecified and out of tree _kernel_ modules (such as systemtap). It
doesnt support any 'application' per se. It basically removes the
kernel's freedom at
On Sat, 23 Jan 2010, Kyle Moffett wrote:
Now how do we get from here to a moderately portable API for
interrogating, controlling, and intercepting process state?
Umm? ptrace?
It's not _pretty_, but it's a hell of a lot more portable than utrace is
ever going to be. Yes, the details differ
