> On Wed, Jun 21, 2023 at 08:22:54PM +0200, developer@robert-palm.de wrote:
>>
>> Quoting Theo Buehler <tb@theobuehler.org>:
>>
>> > > Anybody knows why this happens on arm64 ?
>> > >
>> > > ws-4# uname -a
>> > > OpenBSD ws-4.my.domain 7.3 GENERIC.MP#2164 arm64
>> > >
>> > > ws-4# screen -v
>> > > Segmentation fault (core dumped)
>> >
>> > Does not happen here. Could you provide a backtrace, please?
>> >
>> > # pkg_delete screen
>> > # pkg_add gdb debug-screen
>> >
>> > Then reproduce the crash and at the gdb prompt type 'bt' and share the
>> > output, please.
>> >
>> > # egdb screen screen.core
>> > (gdb) bt
>>
>> Thank you for your instructions! Here you go:
>>
>> ws-4# pkg_delete screen
>> screen-4.9.0|
>> | 0%Invalid \0 character in pathname for ftlink: SPCRP\0 at
>
> Whoa. This and all the other noise that shouldn't be there smell like
> you have some file system corruption. Also, there is BOCHS showing up...
> Is this virtualized?
>
> I would suggest that you run
>
> sysupgrade -s
> pkg_check
> pkg_add -uV
>
> and try again.
Yes it's a cloud instance. I used a snapshot image from 18th June or so.
ws-4# sysupgrade -s
Fetching from https://ftp.hostserver.de/pub/OpenBSD/snapshots/arm64/
SHA256.sig 100% |*************************************| 1544 00:00
Signature Verified
INSTALL.arm64 100% |************************************| 39925 00:00
base73.tgz 100% |*************************************| 266 MB 00:07
bsd 100% |*************************************| 15873 KB 00:00
bsd.mp 100% |*************************************| 15943 KB 00:00
bsd.rd 100% |*************************************| 17511 KB 00:00
comp73.tgz 100% |*************************************| 71020 KB 00:02
game73.tgz 100% |*************************************| 2720 KB 00:00
man73.tgz 100% |*************************************| 7836 KB 00:00
xbase73.tgz 100% |*************************************| 48886 KB 00:01
xfont73.tgz 100% |*************************************| 22968 KB 00:00
xserv73.tgz 100% |*************************************| 10570 KB 00:00
xshare73.tgz 100% |*************************************| 4585 KB 00:00
Verifying sets.
Fetching updated firmware.
fw_update: added none; updated none; kept none
Upgrading.
Then my ssh connection was killed and machine got stuck (see attached
screenshot). Did a reboot then.
ws-4# pkg_check
Packing-list sanity: ok
Direct dependencies: ok
Reverse dependencies: ok
Files from packages: ok
ws-4# pkg_add -uV
quirks-6.133 signed on 2023-06-19T09:15:25Z
ws-4# pkg_delete screen
can't delete screen-4.9.0 without deleting debug-screen-4.9.0
Delete them as well ? [y/N/a] y
debug-screen-4.9.0: ok
screen-4.9.0: ok
Read shared items: ok
--- -screen-4.9.0 -------------------
You should also remove /etc/screenrc (which was modified)
ws-4# pkg_add gdb debug-screen
quirks-6.133 signed on 2023-06-19T09:15:25Z
debug-screen-4.9.0:screen-4.9.0: ok
debug-screen-4.9.0: ok
ws-4# egdb screen screen.core
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-unknown-openbsd7.3".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from screen...
Reading symbols from /usr/local/bin/.debug/screen.dbg...
[New process 330663]
Core was generated by `screen'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000001341903958 in ?? ()
(gdb) bt
#0 0x0000001341903958 in ?? ()
#1 0x000000134190377c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
No comments:
Post a Comment