Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: Stonesense Segentation fault  (Read 1150 times)

GandalfTheGreyt3791

  • Bay Watcher
    • View Profile
Stonesense Segentation fault
« on: July 24, 2020, 02:31:48 pm »
when I try to to launch Stonesense overlay on linux, a new window opens then crashes and the terminal I launch from gives me the error Segmentation Fault. is there anything I can do for this or will I not be able to use it. I'm using elementary os if it matters.
Logged

anewaname

  • Bay Watcher
  • The mattock... My choice for problem solving.
    • View Profile
Re: Stonesense Segentation fault
« Reply #1 on: July 31, 2020, 02:34:10 am »
I have the same error (on Kubuntu and Ubuntu).

I set the stonsense/init.txt to
[DEBUGMODE:YES]
[VERBOSE_LOGGING:YES]
[LOG_IMAGECACHE:YES]

When starting stonesense, it displays:
Stonesense launched
Using allegro version 5.0.10 r1
New image: stonesense/objects.png
New image: stonesense/creatures.png
New image: stonesense/ramps.png
New image: stonesense/SSStatusIcons.png
[DFHack]# Segmentation fault (core dumped)
//
And looking in the GUI.cpp, you can see search for those filenames and see where it is failing.

If you change those init.txt settings and run it, does it return the same output? I noted that github shows SSStatusIcons.png and SSProfIcons.png have not been modified for years, so I am not sure what to try.
Logged
Quote from: dragdeler
There is something to be said about, if the stakes are as high, maybe reconsider your certitudes. One has to be aggressively allistic to feel entitled to be able to trust. But it won't happen to me, my bit doesn't count etc etc... Just saying, after my recent experiences I couldn't trust the public if I wanted to. People got their risk assessment neurons rotten and replaced with game theory. Folks walk around like fat turkeys taunting the world to slaughter them.

Rose

  • Bay Watcher
  • Resident Elf
    • View Profile
Re: Stonesense Segentation fault
« Reply #2 on: July 31, 2020, 04:15:17 am »
There's a new DFHack coming out soon that hopefully has this fixed.
Logged

anewaname

  • Bay Watcher
  • The mattock... My choice for problem solving.
    • View Profile
Re: Stonesense Segentation fault
« Reply #3 on: July 31, 2020, 06:29:54 am »
Excellent! I found the bug discussion here on github and tried out the new stonesense plugin from the automated builds link and it works (but, I did need to revert the three changes made to the init.txt, else it would crash while loading dwarf hair styles).

When closing the stonesense window (using the X in the corner), it does kill DF also. I don't know if this usually happens with stonesense, so I captured the ./dfhack -g output:
[DFHack]# stonesense
[New Thread 0x7fffb5753700 (LWP 1705)]
[New Thread 0x7fffb4f52700 (LWP 1706)]
Stonesense launched
Using allegro version 5.0.10 r1
[DFHack]# [New Thread 0x7fff7f5dc700 (LWP 1707)]
[New Thread 0x7fff7e45b700 (LWP 1708)]
[New Thread 0x7fff7dc5a700 (LWP 1709)]
[Thread 0x7fff7dc5a700 (LWP 1709) exited]
[New Thread 0x7fff7dc5a700 (LWP 1713)]
[Thread 0x7fff7dc5a700 (LWP 1713) exited]

Thread 13 "Dwarf_Fortress" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffb4f52700 (LWP 1706)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Logged
Quote from: dragdeler
There is something to be said about, if the stakes are as high, maybe reconsider your certitudes. One has to be aggressively allistic to feel entitled to be able to trust. But it won't happen to me, my bit doesn't count etc etc... Just saying, after my recent experiences I couldn't trust the public if I wanted to. People got their risk assessment neurons rotten and replaced with game theory. Folks walk around like fat turkeys taunting the world to slaughter them.

Rose

  • Bay Watcher
  • Resident Elf
    • View Profile
Re: Stonesense Segentation fault
« Reply #4 on: July 31, 2020, 10:50:13 am »
That's a longstanding bug that nobody knows how to fix, mostly related to the way Stonesense loads another graphics library on top of DF.
Logged