From nobody Mon Sep 02 15:10:58 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WyBzW72Wzz5TYts for ; Mon, 02 Sep 2024 15:11:19 +0000 (UTC) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from mail.punkt.de (mail.punkt.de [IPv6:2a00:b580:8000:11:1c6b:7032:35e9:5616]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WyBzT0Yn8z4lYh for ; Mon, 2 Sep 2024 15:11:16 +0000 (UTC) (envelope-from wolfgang@lyxys.ka.sub.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=lyxys.ka.sub.org; spf=pass (mx1.freebsd.org: domain of wolfgang@lyxys.ka.sub.org designates 2a00:b580:8000:11:1c6b:7032:35e9:5616 as permitted sender) smtp.mailfrom=wolfgang@lyxys.ka.sub.org Received: from punkt.de (unknown [IPv6:2a00:b580:a000:b000::1000]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.punkt.de (Postfix) with ESMTPSA id E51D23D3EA for ; Mon, 2 Sep 2024 17:11:07 +0200 (CEST) Date: Mon, 2 Sep 2024 17:10:58 +0200 From: Wolfgang Zenker To: freebsd-ports@freebsd.org Subject: lang/php8X whith databases/php8X-sqlite3 and databases/sqlite3 segfaults in Quarterly Message-ID: List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: private site User-Agent: Mutt/2.2.13 (2024-03-09) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.76 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.961]; DMARC_POLICY_ALLOW(-0.50)[lyxys.ka.sub.org,none]; R_SPF_ALLOW(-0.20)[+a:mail.punkt.de]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:16188, ipnet:2a00:b580::/32, country:DE]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4WyBzT0Yn8z4lYh Hello, I have a problem with using the PHP sqlite3 module in the 2024Q3 branch. Scripts segfault on calling $dbObj = new SQLite3('example.db'); Tested with php 8.2 and 8.3, strongly suspect the other versions have the problem as well. For which port(s) should I open a problem report here? The culprit could be either the php-port, the php-sqlite3 subport or the sqlite3 port. I built a small test environment and the sqlite3 cli tool works ok, and I don't see much changes in the php-sqlite3 subports, so I suspect the problematic part is in the php ports. The problem did not exist in the 2024Q2 branch and does not exist in HEAD. Does it make sense to open problem reports on the quarterly branch at all or should I ask the maintainers to MFH the php and sqlite3 ports? Looking forward to your suggestions. Wolfgang