From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 43854 invoked by alias); 30 Oct 2018 22:33:41 -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 43825 invoked by uid 89); 30 Oct 2018 22:33:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=BAYES_00,HTML_MESSAGE,KAM_NUMSUBJECT,KHOP_DYNAMIC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=H*c:alternative, H*c:HHH X-HELO: mx0b-00279001.pphosted.com Received: from mx0b-00279001.pphosted.com (HELO mx0b-00279001.pphosted.com) (148.163.159.148) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 30 Oct 2018 22:33:37 +0000 Received: from pps.filterd (m0112514.ppops.net [127.0.0.1]) by mx0b-00279001.pphosted.com (8.16.0.23/8.16.0.23) with SMTP id w9UMPtoL031317 for ; Tue, 30 Oct 2018 17:33:35 -0500 Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0082.outbound.protection.outlook.com [207.46.163.82]) by mx0b-00279001.pphosted.com with ESMTP id 2nck68u6ve-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for ; Tue, 30 Oct 2018 17:33:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lifesize.onmicrosoft.com; s=selector1-lifesize-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UOlLIsHzOtCKvrjx27CoMu6Iqf5J+qt7QxXX3T9bJXE=; b=h9cTS9NH0kvebfLT1ybFB4yWAM59RRhSYR+JYkU1i0vSZakp0qyUpOvnqHA47LmzL2yRk8od25ijHzUieHO1yszSEJBFbc89U+MKQE0VmnetThSmixnSY0NrZALe/Ev7caPT/XowSX94UjyXu29ocwOjOItv7yCve0K3aBKTHks= Received: from CY4PR15MB1446.namprd15.prod.outlook.com (10.172.161.15) by CY4PR15MB1479.namprd15.prod.outlook.com (10.172.161.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.21; Tue, 30 Oct 2018 22:33:33 +0000 Received: from CY4PR15MB1446.namprd15.prod.outlook.com ([fe80::2140:e32e:b04b:4895]) by CY4PR15MB1446.namprd15.prod.outlook.com ([fe80::2140:e32e:b04b:4895%5]) with mapi id 15.20.1273.027; Tue, 30 Oct 2018 22:33:33 +0000 From: Min Wang To: "gdb@sourceware.org" Subject: gdb next command seem generate signal 0 Date: Tue, 30 Oct 2018 22:33:00 -0000 Message-ID: received-spf: None (protection.outlook.com: lifesize.com does not designate permitted sender hosts) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00062.txt.bz2 Hi I am using gdb: 8.2-0ubuntu1~16.04.1 inside a container which was hosted o= n a debian 9 with Docker version 18.06.1-ce, build e68fc7a. We have a program which catch some linux signal. I set a breakpoint somewhere, the gdb can hit that breakpoint, every time I ran next command, I got signal 0 passed to our program. Is it a bug in gdb? It seems there is no way to catch signal 0 in gdb. If not, could some one explain it? why the signal 0? thanks min