On 1/3/24 19:31, Stuart Henderson wrote:
> On 2024/01/03 19:13, Hukadan wrote:
>> On 1/1/24 14:55, Henrik Friedrichsen wrote:
>>> On Sun, Dec 31, 2023 at 04:15:00PM +0100, Henrik Friedrichsen wrote:
>>>> Unfortunately I'm not experienced with Go port maintenance, otherwise I
>>>> would have updated to 0.13.0 as well.
>>>
>>> Decided to have a go at this and updated the port to 0.13.0. One caveat:
>>> I built it with go-1.21.1 from OpenBSD 7.4, so would be good if someone
>>> could test it with a -CURRENT setup.
>>>
>>> Builds and works fine on arm64.
>>
>> Hi,
>>
>> Thanks for trying on arm64. I had the diff ready for
>> the latest version but, unfortunately, the port is
>> broken on -CURRENT at the moment.
> 
> OOI, just with sqlite or also pgsql?
> 
It crashes at start regardless of the database with the
following message:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1c8835c]

goroutine 1 [running]:
modernc.org/libc.(*TLS).setErrno(0x40d6080?, {0x2260aa0?, 0x2c09060?})
	modernc.org/libc@v1.29.0/etc.go:190 +0xdc
modernc.org/libc.Xmalloc(0xc0000bd520?, 0x2c1e110?)
	modernc.org/libc@v1.29.0/mem.go:34 +0xc5
modernc.org/libc.init()
	modernc.org/libc@v1.29.0/libc_openbsd.go:49 +0x1db

>> I did not have time to investigate further and, most
>> probably, I do not have the skills to fix the issue.
>> I will try to have another look this weekend.
> 
> Running under ktrace and showing the last page or two of kdump output
> may suggest some directions to look at.
> 

I did a kdump when I had the issue but, with the end of the
year festivities, I had no time to share it here.
https://gist.github.com/Hukadan/6b6e3a4555b1045544c93d1d2f31da90
(not the best pastebin I admit)

Regards,

Hukadan