[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060725191221.GA10641@elte.hu>
Date: Tue, 25 Jul 2006 21:12:21 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Olaf Hering <olh@...e.de>
Cc: Linus Torvalds <torvalds@...l.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>, Andi Kleen <ak@...e.de>,
Albert Cahalan <acahalan@...il.com>, arjan@...radead.org,
akpm@...l.org, linux-kernel@...r.kernel.org,
Roland McGrath <roland@...hat.com>
Subject: Re: utrace vs. ptrace
* Olaf Hering <olh@...e.de> wrote:
> 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?
FYI, the sample utrace module from Roland does precisely that, it stops
a task on crash... See more at:
http://people.redhat.com/roland/utrace/
- crash-suspend.c is the sample module.
- ntrace-0.0.2.tar.bz2 is an extensive ptrace and utrace functionality
testsuite.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists