Calling the program in /proc/sys/kernel/core_pattern when it is a pipe
even on ulimit 0 is a design choice, not a bug. We do not want to enable
ulimit -c gemerally just for getting apport reports, since that would
clutter the system with core files. (This now made it into the upstream
kernel, too.)
I'm marking this as "Won't Fix" against linux-source-2.6.17. It's the
same reason for why it was marked "Won't Fix" against linux-
source-2.6.20. Thanks!
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Won't Fix
--
Apport generates a report on SIGQUIT
https://bugs.launc
I'm marking this as "Won't Fix" against linux-source-2.6.20 as it does
not meet the criteria for a stable release update. You can learn more
about the stable release update process at
https://wiki.ubuntu.com/StableReleaseUpdates . However, we'll hopefully
get this fixed in the actively developed
Yes still a problem on gutsy with standard kernel:
2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
--
Apport generates a report on SIGQUIT
https://bugs.launchpad.net/bugs/62511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
Hi Padraig,
Can you confirm this is still an issue with the new 7.10 Gutsy Gibbon
release (2.6.22-14 kernel). Thanks!
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided => Low
Status: New => Incomplete
--
Apport generates a report on SIGQUIT
https://bugs.launchpad.net/
On a debian sarge system with updated kernel to 2.6.20-1
I see the expected good behaviour also:
[EMAIL PROTECTED] echo "|/bin/true" > /proc/sys/kernel/core_pattern
[EMAIL PROTECTED] ulimit -c 0
[EMAIL PROTECTED] cat #hit Ctrl-\ now
Quit
--
Apport generates a report on SIGQUIT
https://bugs.launc
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: New
--
Apport generates a report on SIGQUIT
https://bugs.launchpad.net/bugs/62511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
wrt the kernel ignoring the crashdump helper for SIGQUIT,
it should be ignoring anyway as `ulimit -c 0` was set!
I.E. there seems to be an ubuntu specific bug here in that
the apport helper (or whatever is in /proc/sys/kernel/core_pattern)
is called even when one does `ulimit -c 0`
I tested Fedora
apport (0.23) edgy; urgency=low
.
* apport: Reset signal handler to SIG_IGN in the crash signal handler, to
avoid an endless crash/handler loop (noticed during debugging LP#61708).
* debian/apport.init: Do not let the script run with set -e, so that
do_{start,stop} can deliver the
I'm going to ignore SIGQUIT core dumps in apport, but it would be nice
if the kernel would not call the crashdump helper and dump core for
SIGQUIT in the first place, so that we do not waste the resources.
** Also affects: linux-source-2.6.17 (Ubuntu)
Importance: Undecided
Status: Unconf
apport is called whenever the kernel would create a core dump, and
currently SIGQUIT is in the set of signals which trigger a core dump.
However, I agree that apport should just ignore these.
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
Status: Unconfirmed => In Progress
11 matches
Mail list logo
