From: Dmad <dmadhatr@sdf.org>
To: 9front@9front.org
Subject: [9front] 9Front Drawterm Code 139 Sig 11 SIGSEGV
Date: Fri, 22 Sep 2023 19:11:07 +0000 (UTC) [thread overview]
Message-ID: <8ea3b9d6-c797-179b-cf09-860ebbb4ade5@sdf.org> (raw)
Hardware: IBM Thinkpad T460S
OS: FreeBSD 13.2-STABLE
CPU: Intel i7-6600U (4) @ 2.800GHz
GPU: Skylake GT2 [HD Graphics 520]
Memory: 2445MiB / 20284MiB
Shell: BASH/FISH/ZSH
Version: 9Front drawterm current
Port: Not using port version of drawterm
Ran git command, copied over drawterm.
Ran CONF=freebsd make
made file
ran drawterm command specifc to SDF server
got drawterm connect, put in password
connects
drawterm message:
cpu failed to chdir to '/usr/home/myuser/drawterm'
exits
shell (any of the three) [SIGSEGV]
Job 1, './drawterm -h 205.166.XX.XXX -a' terminated by signal SIGSEGV
(Address boundary error)
echo exit status on $? is 139
tail on messages/dmesg (same):
kernel: pid 78299 (drawterm), jid 0, uid 1002: exited on signal 11
Similar configuration works fine on debian, so I'm not able to produce
the error there. Permissions for folders are similar. Opened up the
drawterm folder with a recursive perm of 777,
even sudo'd the command, same error.
no dumps I coud find, so no help there.
Let me know if anyone has any advice on how to debug/troubleshoot.
Really appreciate your time, beat the shit out of the internet trying to
find an answer on the lists/forums/etc.
/usr/games/catclock misses me.
Cheers,
DMad
dmadhatr@sdf.org
SDF Public Access UNIX System - http://sdf.org
next reply other threads:[~2023-09-22 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 19:11 Dmad [this message]
2023-09-22 19:55 ` hiro
2023-09-23 13:44 ` Dmad
2023-09-23 1:10 ` Amavect
2023-09-23 13:52 ` Dmad
2023-09-23 16:04 ` Dmad
2023-09-23 17:32 ` Dmad
2023-09-24 1:39 ` Dmad
2023-09-24 2:28 ` Sigrid Solveig Haflínudóttir
2023-09-24 2:40 ` Dmad
2023-09-24 3:11 ` Dmad
2023-09-24 3:24 ` Dmad
2023-09-24 4:44 ` Amavect
2023-09-24 15:13 ` Dmad
2023-09-27 4:45 ` Amavect
2023-09-25 13:54 ` Xiao-Yong Jin
2023-09-25 14:47 ` Dmad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ea3b9d6-c797-179b-cf09-860ebbb4ade5@sdf.org \
--to=dmadhatr@sdf.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).