Gordan,
sorry for the absence, I've been swamped with C8, and now with
C7.7, not to mention $dayjob.
I have no theories at the moment, and if I'd love to help once
both versions are out.
Pablo.
Pablo, I don't suppose you (or anyone else here) has had any ideas on how to get any further in debugging this?
On Wed, Jul 31, 2019 at 10:21 PM Gordan Bobic <gordan@redsleeve.org> wrote:
Hmm, after a lot of debuginfo chasing, rebuilding packages where I couldn't find them, different gdbs I have hit a dead end again.No missing debuginfos reported, SIGILL still happens, but backtrace says it can't read memory at address 0x2c.In step through mode, the last it comes up with is:
796 reshape(winWidth, winHeight);798 event_loop(dpy, win);
and then it SIGILLs...
I never thought it would be so difficult to find out what library function is executing when SIGILL gets emitted. :-(
On Wed, Jul 24, 2019 at 11:42 AM Pablo Sebastián Greco <pablo@fliagreco.com.ar> wrote:
El 23/7/19 a las 17:41, Gordan Bobic escribió:
That is devtoolset-7 (basically gcc 7.x, gdb 8.x and others. you can find the armhfp version here https://buildlogs.centos.org/c7-devtoolset-7.armhfp/On Tue, 23 Jul 2019, 21:35 Pablo Sebastián Greco, <pablo@fliagreco.com.ar> wrote:
El 23/7/19 a las 15:36, Gordan Bobic escribió:
I've had some problems using stock gdb, so I generally use gdb from dts-7Joy. 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?
My acronym-fu is weak. What is dts-7?
Pablo.