Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108328 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 58321 invoked from network); 30 Jan 2020 04:48:57 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Jan 2020 04:48:57 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0FD0F1804D1 for ; Wed, 29 Jan 2020 18:59:46 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS8075 40.64.0.0/10 X-Spam-Virus: No X-Envelope-From: Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10olkn2067.outbound.protection.outlook.com [40.92.42.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 29 Jan 2020 18:59:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NN9PwzOYjKMDjP6oVm4nDkeHJvjG/u7EPc23QoeYPXp1VvCZ+MTt3qJkba1r6ldkOuucy3hwyM3NN9AdX6dIx4M5KnQXDwFhjzfTihhjeGuQRHVN/k+GLmixaSPOYM2IRUPyNiG40P/3BntXqsBu6IX+OBVFIjxInwN1GPQVLfrZr/EGRrVOf/bGhtxk0HZhLJ69E758T7Z0aqaMDQw8sIcbZjvFn7zvdrY0p16yKItuHiIe97mcO5IqKa+q11DqXndff290aKPOFS7TyxYrSnJD9bgG4/UjSzXVpZiI06uRnDhRTxIcb0scSUuA9eLs++nAKiB0J49qoBmgX3JNdw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CFQU7hG9PR/Sxy1rAct0/d17szgBsGEeRiQNwn4FGCU=; b=fTmV0hzgEyQNtOsqorp9PTKKQve1KQ3KGiUIsgdJKV12CLhN0vdUVsArO4XfLqdlCDbXzYcd66XDQH7b5ZoSIrCmzZqvvAYiEwmt810wMhpzE5XekuyYB7qt6tYiSGsz5MIQXzeodET+9/n8YB/bzAx846xTo21LusxXwNJocLOOKRlkuOMscx2cT1FFKdCoHWFE+3qz0R6hxL/IzNVEY7wurgeDGeggdsDS8PdeVNV9yhTBgYWISaIohb5T8vP3kpvEI2XJtr+DwJN76ZiiBIlb+jeRpl06If94wxM2KFAtTRNpeYYPxW+7JiBXjEpJEJoXcPhT6SaqOeYLQQ/65Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CFQU7hG9PR/Sxy1rAct0/d17szgBsGEeRiQNwn4FGCU=; b=gtjgIKub8vKS/sJZvlro9lNkdRH2KSDZMlcr/17z4hEnJuQ18QGqRz4h8E5P0mwVwkqAluhexuWX1HdM7c/OnW9bVVmzphrM8NWbH/lDGXw5JNtiDze/mu04ONX/pegccAiP06g82eSrTBZfQWfp85p46ssBbmpLuE7rGwVKLPWN0EGkcGFpyzA4qiXR8zPRBhKM7+ETGI5NhNi4esLmo8dOCtLzc1ftH5YuiB997YDSg/SCtoLvUqKFJ9tO5PyHarYcgYVu08cQh+j2CxwIHnoNtiB9FEwNaZ3CE7+n9iI6gZyKvCX9DNUHPxlKUhGwvf1cNsiIU+5y6IktLgoxcw== Received: from MW2NAM10FT003.eop-nam10.prod.protection.outlook.com (10.13.154.59) by MW2NAM10HT062.eop-nam10.prod.protection.outlook.com (10.13.154.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18; Thu, 30 Jan 2020 02:59:43 +0000 Received: from DM5PR07MB3067.namprd07.prod.outlook.com (10.13.154.58) by MW2NAM10FT003.mail.protection.outlook.com (10.13.155.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.25 via Frontend Transport; Thu, 30 Jan 2020 02:59:42 +0000 Received: from DM5PR07MB3067.namprd07.prod.outlook.com ([fe80::29e3:53bf:163e:5beb]) by DM5PR07MB3067.namprd07.prod.outlook.com ([fe80::29e3:53bf:163e:5beb%3]) with mapi id 15.20.2665.027; Thu, 30 Jan 2020 02:59:42 +0000 To: Benjamin Morel , "bishop@php.net" CC: PHP Internals Thread-Topic: [PHP-DEV] How to debug a segmentation fault? Thread-Index: AQHV1fgMRGyLBah1gUGPr6kq4bV9NagB5IcAgABe1YCAADypQYAAAmf6gAACbPg= Date: Thu, 30 Jan 2020 02:59:42 +0000 Message-ID: References: ,,, In-Reply-To: Accept-Language: en-CA, en-US Content-Language: en-CA X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:96F06A440195461EC434AC3BF303BEC7574EFD5C6524EFEAF9C80D142E435C26;UpperCasedChecksum:563F2A77395813E2997E7139603D27786BF98DF8209C1015D8F4FEA55D2A7D9E;SizeAsReceived:7365;Count:46 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [H79gCye+Qvkgb4DmdKVKraVcYv5lfCsn] x-ms-publictraffictype: Email x-incomingheadercount: 46 x-eopattributedmessage: 0 x-ms-office365-filtering-correlation-id: f990d990-a3f5-4e80-31cb-08d7a530749b x-ms-traffictypediagnostic: MW2NAM10HT062: x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: c79C9BfI9u2ge23NpYdOhet3fQoUqRJxOmrjsq4w7RLbSTJ7f08ySgCMF2clJONI3MZSF4k8ahfiZw7zGRY4ygzEEev9JSsKBnWf4dt6cu1P4CsbQTo9CN5hZQuF+J4rA/CIOtAwClxtkjoS6qf9l893mqoIcCjdizXqLrVJLhbfUWcqG/tHN/JibjwT9Wrt+Q8eZc7PvKSAzmC3IPmWA3CX+Fin5YEVmGDOGZJbOQs= x-ms-exchange-antispam-messagedata: +MwIB7WfDziJQaBTqeyAg4+YClOgDdIqXNEATlg69PKSuWGVsCPbevsRVW7ZGgz2NSEgtEXO8AlDqb7oXBQknPv9eIekaD9rphuknAjcFI2Kpu8hGwIw5L550i8VuunCgEdjcueyftEoCgyTCskaHA== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: f990d990-a3f5-4e80-31cb-08d7a530749b X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jan 2020 02:59:42.9145 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2NAM10HT062 Subject: Re: [PHP-DEV] How to debug a segmentation fault? From: tysonandre775@hotmail.com (tyson andre) > Sorry, I didn't notice that=A0https://bugs.php.net/bug.php?id=3D79194=A0w= as already [solved and] closed with a similar answer.=0A= =0A= In addition to phpspy, a tool I forgot to mention was Phan. (https://github= .com/phan/phan)=0A= =0A= `phan --redundant-condition-detection` will enable many of Phan's checks, i= ncluding code that looks like a function or method calling itself unconditi= onally, or with the same args.=0A= I got the idea for adding a check for PhanInfiniteRecursion (and=A0PhanPoss= iblyInfiniteRecursionSameParams) after investigating a similar segfault ove= r a year ago ago=0A= (and considering most of those solutions),=0A= to detect that type of bug before it ran.=0A= https://github.com/phan/phan/blob/master/internal/Issue-Types-Caught-by-Pha= n.md#phaninfiniterecursion has an example of what it detects=