10:12:52 <andyf> hpqoeu - would you be willing to share that core?
10:13:32 <andyf> It will be a native illumos one so usually mdb can make some sense of at least the high level, otherwise it is possible to run the omnios gdb on it from the global zone.
14:17:41 <hpqoeu> sure, where can i upload it?
15:02:31 <hpqoeu> andyf: anything else you would need outside of the core file?
18:32:33 <andyf> The binary that generated it wouldn't hurt either, but I just wanted to take an initial look and see if there is any information on what type of failure this was
18:32:49 <andyf> We know that 'lx' is not a perfect emulation but we also try and make it work when possible
20:31:37 <hpqoeu> andyf: https://host.vintergatan.space/piFu6/QIjIVoYE79.core , from my own filehosting, if it doesn't work i can upload it to google drive or similar i guess
20:51:28 <andyf> Thanks, I'll take a look. The first thing is that it seems to have called abort() so there might be something useful at the end of one of the files in /home/pro/.local/share/Steam/logs/
20:51:57 <andyf> 'stderr.txt' perhaps?
21:03:25 <hpqoeu> it's completely empty
21:03:33 <hpqoeu> -rw-r--r-- 1 pro pro 0 Jan 17 23:29 stderr.txt
21:05:12 <hpqoeu> oh, reminds me, i was getting errors about 'netlink', but i wasn't sure if that was part of the wrapper script/package that uses steamcmd under the hood
21:07:42 <hpqoeu> and it was spewing errors about /tmp/dump i think complaining about it not being read/writeable even after i chmod 777'd it, and redirecting the output to the stderr.txt file instead
21:13:10 <andyf> I'll see what I can dig out of that core, but this could well be a case where you're hitting the limits of the emulation and need to look at bhyve instead
21:15:35 <hpqoeu> yeah, that was gonna be my solution, i just came here with the problem to see if i could learn anything and maybe if it's a known thing