Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Feb 2015 18:16:01 -0500
From:      Benjamin Kaduk <bjkfbsd@gmail.com>
To:        Rui Paulo <rpaulo@freebsd.org>
Cc:        "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>
Subject:   Re: svn commit: r278479 - in head: etc sys/kern
Message-ID:  <CAJ5_RoDC6dakjcc76fFEPsM6OOZkENj=ZVbXEHSVgKs5ap0xoQ@mail.gmail.com>
In-Reply-To: <201502092313.t19NDpoS083043@svn.freebsd.org>
References:  <201502092313.t19NDpoS083043@svn.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 9, 2015 at 6:13 PM, Rui Paulo <rpaulo@freebsd.org> wrote:

> Author: rpaulo
> Date: Mon Feb  9 23:13:50 2015
> New Revision: 278479
> URL: https://svnweb.freebsd.org/changeset/base/278479
>
> Log:
>   Notify devd(8) when a process crashed.
>
>   This change implements a notification (via devctl) to userland when
>   the kernel produces coredumps after a process has crashed.
>   devd can then run a specific command to produce a human readable crash
>   report.  The command is most usually a helper that runs gdb/lldb
>   commands on the file/coredump pair.  It's possible to use this
>   functionality for implementing automatic generation of crash reports.
>
>   devd(8) will be notified of the full path of the binary that crashed and
>   the full path of the coredump file.
>

What advantage does putting this in devd have over a standalone daemon for
crash reporting?  Is it just the ease of implementation to leverage the
existing infrastructure?

-Ben



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ5_RoDC6dakjcc76fFEPsM6OOZkENj=ZVbXEHSVgKs5ap0xoQ>