From: Olaf Hering <olh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>, Albert Cahalan <acahalan@gmail.com>,
arjan@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
Roland McGrath <roland@redhat.com>
Subject: Re: utrace vs. ptrace
Date: Tue, 25 Jul 2006 20:57:44 +0200 [thread overview]
Message-ID: <20060725185744.GA15844@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0607251124080.29649@g5.osdl.org>
On Tue, Jul 25, Linus Torvalds wrote:
> What you often want is not a core-dump at all, but a "stop the process"
> thing. It's really irritating that the core-dump is generated and the
> process is gone, when it would often be a lot nicer if instead of
> core-dumping, the process was just stopped and then you could attach to it
> with gdb, and get the whole damn information (including things like access
> to open file descriptors etc).
>
> But again, that has nothing to do with core-dumping.
It would be helpful to have that sort of functionality in mainline.
Would a patch be acceptable that sends SIGSTOP instead of SIGSEGV or
SIGILL if some knob was enabled, either global or per process?
next prev parent reply other threads:[~2006-07-25 18:57 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
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 [this message]
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=20060725185744.GA15844@suse.de \
--to=olh@suse.de \
--cc=acahalan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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