Hello Trondelag,
you tried to build from the v2.5.2 tarball?
What OS/distro are you using and which version?
Please send the output of `uname -a`.
The GDB session doesn't show any details unfortunately.
Please rebuild SciTECO with Debug symbols:
./configure --enable-debug
make clean all
Then start SciTECO under GDB as follows:
gdb --args /usr/local/bin/sciteco filename
(gdb) run
...after the crash...
(gdb) bt
Alternatively, enable coredumps:
uname -c unlimited
sciteco filename
Find the coredump and run
gdb sciteco coredump
(gdb) bt
As a workaround you can also try building from the master branch -
it's quite stable, I am also daily driving it.
Best regards,
Robin
On Thu Oct 1, 2026 at 23:10:00 GMT +02, Trondelag wrote:
> sciteco segfaults on open file.
> This is tested with the last stable release, 2.5.2, ncurses and gtk
> (gdb) break main
> Breakpoint 1 at 0xe438e
> (gdb) run
> Starting program: /usr/local/bin/sciteco
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
>
> Breakpoint 1, 0x000055555563838e in main ()
> (gdb) s
> Single stepping until exit from function main,
> which has no line number information.
> Downloading 1.43 K source file /usr/src/debug/glibc/glibc/signal/sigaction.c
> 0x00007ffff763e63c in __GI___sigaction (sig=2, act=0x5555558a7760 <sigint>, oact=0x0)
> at sigaction.c:28
> 28 if (sig <= 0 || sig >= NSIG || is_internal_signal (sig))
> (gdb)
--
_at_ii._._.*.._+__.+_+.+...+.+.++..+*+.+._.+...*_*.*.__+__._._.++..+_*.++__+__
.+_..*...+.+_+__.+._.+...*_+_+__._ ...*_ +.+._.+.._+*+_+__._._ .+_..+.+***_
. *_+_+__.+.*.++..+_+.*.__+_ _.+...*_*_+__.++*.+...++..+* +.+.._+__._+_.+..
.++..+*_.*...+*+.+.*_ +*+i2^rj.u#__%uu#_.%uu#_+%uu#_*!+!0a"t1010^t^c^c'0a^#
1010"=d'0a-100000"=d'0auuqq*100+q[_^euu]uq-rq:^/100_at_oo,+,+,+oqq^t0uq_at_o*+*!!
Received on Fri Oct 02 2026 - 00:05:09 CEST