Comment 19 for bug 1767826

I have added extra asserts, but they are active only in the debug builds. I may add dumping stacktraces whenever an anomaly in a DLIST object is detected, but most likely it will require symbol visibility setting change (-fvisibility and -fvisibility-inlines-hidden) that may result in larger binary files. I am not sure this is the right thing to do.

It would be highly appreciated if you could build a debug version, so you could observe the asserts. If not, I can prepare a debug build for you and upload it somewhere. I may add an extra patch that continuously checks the tracks list coherency, so any issues will be detected instantly.

By the way, do you use any other tools modifying the tracks? E.g. clean-up tracks or global delete? Are you able to recall the actions you have performed before the crash?