Joy. So missing / mismatching debuginfo warnings are now all resolved, but execution through gdb fails eventually with "Cannot access memory at address ..." gdb/frame.c:445: internal-error: get_frame_id: Assertion `fi->this_id.p' failed. And gdb helpfully offers to dump core. Anyone got any other ideas? On Tue, Jul 23, 2019 at 7:25 PM Gordan Bobic <gordan at redsleeve.org> wrote: > glew there is version 1.9. The distro packages include 1.10. > How did that happen? > > > On Mon, Jul 22, 2019 at 11:11 PM Pablo Sebastián Greco < > pablo at fliagreco.com.ar> wrote: > >> >> El 22/7/19 a las 18:53, Gordan Bobic escribió: >> >> I'm still trying to hunt down where this SIGILL I'm hitting is coming >> from, and the next obstacle I've hit is some missing debuginfo packages, >> specifically: >> libGLEW-debuginfo >> libXau-debuginfo >> libXext-debuginfo >> mesa-libGLU-debuginfo >> >> Any chance those could be added the the debuginfo repository? >> Without them gdb chokes before it gets to the SIGILL line. >> >> Those were built during the first bootstrap, using the old plague server, >> and were never from there. >> You can find the original builds, along with debuginfo here >> https://armv7.dev.centos.org/repodir/c7-pass-1/ >> >> HTH, Pablo. >> >> Gordan >> >> _______________________________________________ >> Arm-dev mailing listArm-dev at centos.orghttps://lists.centos.org/mailman/listinfo/arm-dev >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20190723/7e8a8d39/attachment-0006.html>