From: Theo Buehler <tb@theobuehler.org>
Subject: Re: rustic 0.11.3: coredump on backup
To: bket@openbsd.org, ports@openbsd.org
Date: Tue, 9 Jun 2026 05:36:19 +0200

On Tue, Jun 09, 2026 at 12:33:23AM +0200, Kirill A. Korinsky wrote:
> On Tue, 09 Jun 2026 00:27:51 +0200,
> Stuart Henderson <stu@spacehopper.org> wrote:
> > 
> > are there any clues from ktrace about what the code is doing at the time?
> > 
> 
> I've tried a few times, each trace ends like that:

>  79264 rustic   PSIG  SIGSEGV SIG_DFL code=SEGV_ACCERR addr=0xb8fdd15906f trapno=6
>  79264 rustic   NAMI  "rustic.core"

xonly. Looks like the update switched to aws-lc.

Not sure if the ports tree can help here, if cargo.port.mk emitted a
warning for aws-lc-sys there would likely be many false positives.

Since https://github.com/awslabs/s2n-bignum/pull/242 is now merged,
the problem should also resolve itself soon.

Index: Makefile
===================================================================
RCS file: /cvs/ports/sysutils/rustic/Makefile,v
diff -u -p -r1.33 Makefile
--- Makefile	4 Jun 2026 04:15:13 -0000	1.33
+++ Makefile	9 Jun 2026 03:31:15 -0000
@@ -1,9 +1,16 @@
 # ring-v0.17 does not support this arch
 NOT_FOR_ARCHS =		sparc64
 
+# aws-lc-sys has constants in .text
+# https://github.com/awslabs/s2n-bignum/pull/242
+.if ${MACHINE_ARCH} == "amd64"
+USE_NOEXECONLY =        Yes
+.endif
+
 COMMENT =		fast, encrypted, deduplicated backups
 
 DIST_TUPLE =		github rustic-rs rustic v0.11.3 .
+REVISION =		0
 
 CATEGORIES =		sysutils