From: Ingo Molnar <mingo@elte.hu>
To: Albert Cahalan <acahalan@gmail.com>
Cc: torvalds@osdl.org, ak@suse.de, alan@lxorguk.ukuu.org.uk,
arjan@infradead.org, bunk@stusta.de, akpm@osdl.org,
rlrevell@joe-job.com, linux-kernel@vger.kernel.org,
Roland McGrath <roland@redhat.com>
Subject: Re: utrace vs. ptrace
Date: Thu, 13 Jul 2006 11:24:32 +0200 [thread overview]
Message-ID: <20060713092432.GA11812@elte.hu> (raw)
In-Reply-To: <20060713070445.GA30842@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> utrace enables something like 'transparent live debugging': an app
> crashes in your distro, a window pops up, and you can 'hand over' a
> debugging session to a developer you trust. Or you can instruct the
> system to generate a coredump. Or you can generate a shorter summary
> of the crash, sent to a central site.
not to mention that utrace could be used to move most of the ELF
coredumping code out of the kernel. (the moment you have access to all
crashed threads userspace can construct its own coredump - instead of
having the kernel construct a coredump file) Roland's patch does not go
as far yet, but it could be a possible target.
Ingo
next prev parent reply other threads:[~2006-07-13 9:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 5:43 [patch] let CONFIG_SECCOMP default to n Albert Cahalan
2006-07-13 7:04 ` utrace vs. ptrace Ingo Molnar
2006-07-13 9:24 ` Ingo Molnar [this message]
2006-07-13 12:37 ` Andi Kleen
2006-07-13 12:43 ` Ingo Molnar
2006-07-13 13:21 ` Andi Kleen
2006-07-13 13:28 ` Arjan van de Ven
2006-07-13 13:34 ` Andi Kleen
2006-07-13 13:37 ` Arjan van de Ven
2006-07-13 13:46 ` Andi Kleen
2006-07-13 19:05 ` Linus Torvalds
2006-07-13 19:47 ` Ingo Molnar
2006-07-14 10:42 ` Paul Jackson
2006-07-25 18:49 ` Alan Cox
2006-07-25 18:27 ` Linus Torvalds
2006-07-25 18:57 ` Olaf Hering
2006-07-25 19:12 ` Ingo Molnar
2006-07-26 0:20 ` Martin Bligh
2006-07-13 7:07 ` [patch] let CONFIG_SECCOMP default to n andrea
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060713092432.GA11812@elte.hu \
--to=mingo@elte.hu \
--cc=acahalan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=roland@redhat.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox