ukagaka help

hello, I was working on a lain ukagaka (desktop pet) for a period of time around March, however I switched to a different OS and now I cannot access the program I used beforehand. Ukagaka https://en.wikipedia.org/wiki/Ukagaka SSP (the program I used on windows) ssp.shillest.net ninix-aya http://ninix-aya.osdn.jp/ (for linux) My issue is I was getting a core dumped error for the ninix port of this program. Is there anyway to fix it? Are other people in this community interested in helping with a Lain themed ukagaka? Are other people in the community interested in ukagaka in general too, I can't find many people who are interested in obsolete desktop pets, and I am super autistic about them. Pic related, it's another ukagaka that is very popular in mentally ill children's web circles.

>>63235 You should probably include what you downloaded exactly, which instructions did you follow (did you do the make part for kawari8.so? Or did you only focus on kawari.py?), and which command did you run exactly. If you want to increase your chances of help, also figure out where the corefile is located and upload it for people to analyze. Or figure out where the corefile is and analyze it yourself with gdb (run backtrace and copy-paste the result). You can also try asking in /lambda/. Make sure you appeal to their egos, "you guys are probably not smart enough to figure this out but I'll try anyway...."

>>63241 Thank you for the tips, so I started to compile ninix from source, however it would not work (user error. I am retarded) so I pulled an apt-get out of my asshole and used that. Possible scenario is that the apt is out of date. I don't even think I followed a good set of instructions, as I don't remember seeing the kawari file you are mentioning (neither of them)

>>63274 >I don't remember seeing the kawari file you are mentioning (neither of them) All you gave us to go on is the link in your OP. If you're doing something different then how do you expect anyone to help.

>>63275 Sorry, I wasn't able to find the direct package link earlier in the thread. Here is the one I am using https://debian.pkgs.org/10/debian-main-arm64/ninix-aya_5.0.9-1_arm64.deb.html

sorry for the double post, I see what you mean now. I made this thread on a whim and I should have reread the webpage more clearly. Anyways; I will try again and focus on kawari.py Here is the specific core dump I get https://pastebin.com/Vr0k3KST

thats neat, keep going anon! also love Mayura & diggig up art about her. i can't program anything but would love to see if you ever finish it

>>63235 Is there a location where I can find mascots? I'm having trouble finding them

>>63857 It depends on what you want specifically! If you aren't really into weeb soykaf you have a collection of OC characters that are made modernly, but there's also easy to find resources through forums, discord, and other locations. The best place I've found is a master list made on Google docs by a friend of mine.

>>63866 I'm >>63857 I'd prefer weeb soykaf to be honest, can I get that google doc?

>>63284 >>63235 >My issue is I was getting a core dumped error for the ninix port of this program. >Is there anyway to fix it? Very likely if the source code is available (pls link ITT). But you need to use gdb to get a backtrace. Since you are on Debian, you need to install gdb and build-essential packages. On other distros you need to find a similar meta-package or install the individual packages needed for C/C++ development and building programs (and don't forget to install gdb). In addition to C/C++ toolchain (the packages that come with build-essential) and gdb, you need the debugging symbols (usually there is a separate package_name-debug package). If you are building from source, make sure to make a debug build (better) or add -Og -ggdb -g3 to your CFLAGS (edit the makefile or run make like CFLAGS="-Og -ggdb -g3" make Also, note that each program requires particular CFLAGS (like -std=c99 etc.); copy these from the makefile and put the CFLAGS that are needed for debugging after them like: CFLAGS="-std=c99 -Og -ggdb -g3"! If the project uses autotools, you should cd to dir that contains the source code and run ./configure --help Also, read the README that comes with the source code! It (should) contain important info, like what tools and libraries are needed to compile the program. To actually get the backtrace, open terminal and type (I use $ as the shell/Bash prompt): #you can use --se /path/to_dbgsyms to specify the location where the debug symbols are located. #you can use --core /path/to_coredump to specify the location of the core dump. $ gdb prog #use ./my_prog if you are debugging a binary that's located in your current dir. help run run run fnord run --foobar baz help backtrace backtrace quit #other things you can do in gdb: info locals where # etc. etc. More info: >https://itsfoss.com/install-software-from-source-code/ ^But do not actually build NodeJS (seriously)! Do not use make -j9 unless you have a CPU with 9 threads (and enough RAM)! Use lscpu if you are unsure. Also, be extra careful if you change your $PATH environment variable! It can cause security issues! At first, it best to just build and install stuff on your $HOME dir. >https://wiki.debian.org/DebugPackage >https://wiki.debian.org/HowToGetABacktrace >https://www.cse.unsw.edu.au/~learn/debugging/modules/gdb_coredumps/ (you can also load the core dump in gdb!) >https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces + https://wiki.gentoo.org/wiki/Debugging_with_GDB >https://www.sourceware.org/gdb/current/onlinedocs/gdb.html#Sample-Session FYI, if you use GNU Emacs, it comes with a interface to GDB: https://www.gnu.org/software/emacs/manual/html_node/emacs/GDB-Graphical-Interface.html If you aren't Emacs user, then you can also try DDD (or just stick to the CLI version).

>>63235 is it possible to run the software and develop the ukagaka using a VM of the previous OS while you're trying to figure out how to do it with the new one. That might help