I did some Google research and apparently this is a well known problem on Fedora 28, and not specific to KiCad. Hardening flags were added to the default build parameters, including _GLIBCXX_ASSERTIONS, which "turns on cheap range checks for C++ arrays, vectors, and strings" [1].
There is a minimal example how to trigger (and fix) this problem in the httpuv bug tracker [2]. Maybe this can help to fix this bug in KiCad as well.
I did some Google research and apparently this is a well known problem on Fedora 28, and not specific to KiCad. Hardening flags were added to the default build parameters, including _GLIBCXX_ ASSERTIONS, which "turns on cheap range checks for C++ arrays, vectors, and strings" [1].
There is a minimal example how to trigger (and fix) this problem in the httpuv bug tracker [2]. Maybe this can help to fix this bug in KiCad as well.
[1] https:/ /fedoraproject. org/wiki/ Changes/ HardeningFlags2 8 /github. com/rstudio/ httpuv/ issues/ 133#issuecommen t-387499519
[2] https:/