¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: New Version


 

Update, it crashed when I checked the BBS box on a user where it was previously unchecked, and then clicked "Update". I wasn't doing that when it went down before, so I think this is possibly a different issue. I have restarted it via gdb. It does seem to be more stable using the pre-compiled binary.

That said, I did see "SIGSEGV Received" crashes on the .56 binary (i.e. not compiled) after upgrading from .53, which appeared to be the same that N3MEL and WW6Q saw on the .59 code.

[New Thread 0xab5fd420 (LWP 18985)]
[Thread 0xab5fd420 (LWP 18985) exited]
[New Thread 0xab5fd420 (LWP 18996)]

Thread 269 "linbpq" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xab5fd420 (LWP 18996)]
config_setting_lookup (setting=0x0, path=<optimized out>) at libconfig.c:1206
warning: 1206 libconfig.c: No such file or directory
(gdb) q

I'll wait for an auto-crash this time, which is what happened previously.

73,
Lee K5DAT


On Sun, Feb 16, 2025 at 7:38?AM Lee Bengston via <kilo5dat=[email protected]> wrote:
I decided to start over using the .62 pilinbpq binary from the beta downloads area. I have had problems with compiled versions recently ever since upgrading from Ubuntu 22.04 to 24.04, so I wanted to take that out of the equation. It's running now under gdb - will try to watch it closely.

Thanks,
Lee K5DAT


Join [email protected] to automatically receive all group messages.