From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 80428 invoked by alias); 21 Sep 2017 18:14:58 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 79855 invoked by uid 89); 21 Sep 2017 18:14:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*Ad:D*de.ibm.com, H*Ad:U*uweigand, Hx-languages-length:1388, traditionally X-HELO: mx0a-001b2d01.pphosted.com Received: from mx0a-001b2d01.pphosted.com (HELO mx0a-001b2d01.pphosted.com) (148.163.156.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Sep 2017 18:14:56 +0000 Received: from pps.filterd (m0098394.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v8LIDwcM083663 for ; Thu, 21 Sep 2017 14:14:55 -0400 Received: from e06smtp10.uk.ibm.com (e06smtp10.uk.ibm.com [195.75.94.106]) by mx0a-001b2d01.pphosted.com with ESMTP id 2d4euyc0vd-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Thu, 21 Sep 2017 14:14:55 -0400 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 21 Sep 2017 19:14:53 +0100 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp10.uk.ibm.com (192.168.101.140) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 21 Sep 2017 19:14:51 +0100 Received: from d06av24.portsmouth.uk.ibm.com (d06av24.portsmouth.uk.ibm.com [9.149.105.60]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v8LIEpoi20709570; Thu, 21 Sep 2017 18:14:51 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6887642041; Thu, 21 Sep 2017 19:11:00 +0100 (BST) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3F04C4203F; Thu, 21 Sep 2017 19:11:00 +0100 (BST) Received: from oc1027705133.ibm.com (unknown [9.152.212.164]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTPS; Thu, 21 Sep 2017 19:11:00 +0100 (BST) From: Andreas Arnez To: Jan Kratochvil Cc: Ulrich Weigand , GDB Development Subject: systemd-coredump in distros Date: Thu, 21 Sep 2017 18:14:00 -0000 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-GCONF: 00 x-cbid: 17092118-0040-0000-0000-000003DC15C3 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17092118-0041-0000-0000-000025DD51DA Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-09-21_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709210247 X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00094.txt.bz2 It seems common for new distros to install systemd-coredump by default and disable core files in the current working directory. For instance, see the announcement "Enable systemd-coredump by default" for Fedora 26 (https://fedoraproject.org/wiki/Changes/coredumpctl). Is there a recommended/preferred way to deal with this in a typical development use case? I stumbled upon some issues with systemd-coredump and don't know if I misunderstood something: * In my tests, after invoking a command that dumps core, it could happen that "coredumpctl" failed immediately afterwards and succeeded a second later -- maybe due to asynchronous processing? * There does not seem to be a way for a user to remove core dumps from the journal. Thus a developer's experiment may pile up dumps in the journal, occupying lots of space and making the dumps more difficult to find. * I've seen dumps (from GDB's bigcore.exp) being truncated by coredumpctl down to four Gigabytes, although no such limit was set in /etc/systemd/coredump.conf. Note that I haven't investigated where the truncation happens. Considering these issues I wonder whether there's a way for a user to tell systemd-coredump something like: "Core dumps from this process should be treated traditionally and written to its current working directory". Is that possible? If not, should it be? -- Andreas