Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108947
Message-ID:
 <AM0PR0502MB3668A6EC03DE6149D76B6626C0FF0@AM0PR0502MB3668.eurprd05.prod.outlook.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>, PHP internals
	 <internals@lists.php.net>, internals-win <internals-win@lists.php.net>
Date: Tue, 10 Mar 2020 13:59:32 +0100
In-Reply-To: <df7c743d-e5b8-c588-4e85-2620f97e2356@gmx.de>
References: <df7c743d-e5b8-c588-4e85-2620f97e2356@gmx.de>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Sender: Anatol Belski <weltling@outlook.de>
X-MS-Exchange-MessageSentRepresentingType: 2
Received: from fringe.fritz.box (2001:16b8:26a4:e400:b356:24e:b92a:da21) by AM0PR02CA0055.eurprd02.prod.outlook.com (2603:10a6:208:d2::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17 via Frontend Transport; Tue, 10 Mar 2020 12:59:33 +0000
X-Microsoft-Original-Message-ID:
 <167671d8a23a275d970d89974e4788fd7a0fc855.camel@php.net>
X-TMN: [eS4pvzBCZry86nfuH92fvKLiPVlGbFqLsjnwxR5qqrMXycZqTJzZpoJLydusQ2nR]
X-MS-PublicTrafficType: Email
X-IncomingHeaderCount: 49
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-Correlation-Id: 4a9d2b8b-06d3-4a93-883b-08d7c4f2e103
X-MS-TrafficTypeDiagnostic: DB3EUR04HT090:
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
	W3Ge5u/CtDHibOd/ZfOfseyOGFH2wLLJ4A0MqCJaPgwZ+tjDY/hprJmp64vthmelmSWLEVbHDyruJ+6N9MHmTjA6/SbxSpaLomkNVyxs/XD6WKq0Su6IRter813SLtrk2umDoDY+X5gNZKCMOC8hE48M3gUaCzdyTpvzKvliTsipwbEYqT0zVakySaHi+6VLVe865rN7NbnSNOkSpod1QagaE3MZ9E3TZG3dRW+PNao=
X-MS-Exchange-AntiSpam-MessageData:
	N4cLv2QLAUNxbzS4pWd9xfOEY5mha/Umw6bd3gg2cd8FuVbeELvloTfsuaCn2wHUz9UHyUZc8tOLSK5szTdnt6gjvAz5KmCqa3Y9Bwf2WLzZfMgHbWoCkxYJpxl37BcUfC3CzpwMq/V3xN0lByK9iRZJaZXG/qV/xO43dwm8OtTggZaiXQZmxHc91BUy97vZBb4jI3SOKzdZhUWpPMrAmg==
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4a9d2b8b-06d3-4a93-883b-08d7c4f2e103
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Mar 2020 12:59:33.9555
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg:
	00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3EUR04HT090
Subject: Re: [PHP-DEV] Windows snapshot builds switching to debug
From: ab@php.net (Anatol Belski)

Hi Christoph,

I'd see not much value in switching to debug builds for the snapshots.
Currently the snapshots are public and are built with PGO. This makes
it easy for users to test any provided revision. Debug builds are
better suitable for the runtime development, but they require a debug
runtime, can't use PGO and are in most case unusable for users.

IMO, if debug builds of snapshots are needed for something, they might
be added, but release buids of snapshots should not be removed. It is
more important to ensure release builds, for debug they're also
suitable in 98% of cases as it always contains debug symbols. There are
many other points that would speak against switching to debug builds
only. For the developer needs, debug builds can always be done on
demand.

Regards

Anatol

On Thu, 2020-03-05 at 16:41 +0100, Christoph M. Becker wrote:
> Hi all,
> 
> the PHP for Windows team is considering to ship all PHP snapshot
> builds[1] as debug builds in the future (earliest at the end of
> March);
> currently these are release builds.  The reason for this change is
> that
> debug builds obviously have better debugging support (including but
> not
> limited to WER[2]), and also execute assertions and enable the basic
> leak checking of Zend Memory Manager.
> 
> Of course, the debug builds would be not as performant, and would be
> larger in size, but that does not appear to be an issue for snapshot
> builds.
> 
> Thoughts?
> 
> [1] <https://windows.php.net/snapshots/>
> [2]
> <
> https://docs.microsoft.com/en-us/windows/win32/wer/windows-error-reporting
> >
> 
> --
> Christoph M. Becker
>