On 23/07/14 19:38, Matthias Clasen wrote:
does a good job of describing the different levels of detail and
interactivity that might be desirable for problem reporting.
The overlap with a developer-focused workstation might be interesting -
if you are developing software on the system, you probably don't want to
get a crash collection system to get between your crashing app and the
that's a good point, and it looks like this already works in current
Fedora releases - here /proc/sys/kernel/core_pattern calls
/usr/libexec/abrt-hook-ccpp but it's apparently smart enough to handle
applications that aren't in /usr in the "traditional" way and writes a
core.pid file (if enabled with ulimit); so things like LibreOffice's
build system automatically running gdb to get a backtrace when a unit
test crashes work fine.