ttmkfdir segfaults with twmoefonts. Stack trace and patch coming up. Reproducible: Always Steps to Reproduce: 1. emerge ttmkfdir 2. emerge twmoefonts 3. ttmkfdir -d /usr/share/fonts/twmoefonts Actual Results: segfault. Expected Results: not segfault?
Created attachment 63516 [details] trace Did a recompile with CFLAGS="$CFLAGS -gdwarf-2" FEATURES=nostrip and ran it under gdb using "gdb --args ttmkfdir -d /usr/share/fonts/twmoefonts", I got this backtrace
Created attachment 63517 [details, diff] patch with this patch it doesn't segfault, though I'm not sure if it's a ttmkfdir bug or a libstdc++ bug ...
Just so we have it, attaching your `emerge info` and giving us the version number of the involved packages would be helpful.
Created attachment 63565 [details] emerge info ttmkfdir version 3.0.9-r3 twmoefonts 0.1-r1
Is there a possibility that it's a broken font?
even if it is a broken font, should it not segfault? Maybe the fix should be libstdc++, since it would seem that when a sequence of one is passed to std::unique it crashes...
I just tried compiling with gcc 4.0.0 (installed it a while ago to test it), it doesn't segfault, it seems to be a bug in gcc3.3.5? The patch posted just works around the issue.
Passing it to toolchain folks.
installed gcc-3.4.4-r1 and reinstalled ttmkfdir-3.0.9-r3 and tested with twmoefonts. No crash. Since gcc-3.4.4 is now in stable, this can be considered fixed?
Sounds good to me, thanks.
