Fascinating. This crash only touches us once at Panned.cpp:66. And
that's just a message forward. Unlikely that it is an rg problem. More
likely a Qt5 bug. We might want to try watching for a null event
pointer there, but I have a feeling that never happens as it would cause
an earlier crash (shorter call stack).
Do you have a procedure that starts from an empty composition? Don't
spend any time on it if not. It would just be nice to see if it is
reproducible with Qt6 and Philip could test that very easily.
I'll spend a little time beating it up with some huge compositions I
have lying around.
Ted.
On 1/18/26 5:24 PM, Babarosa wrote:
Please find attached the info. I can reproduce this crash.
Thank you for helping, Michael
Am 18.01.26 um 16:43 schrieb Ted Felix:
Ok. Usually for this kind of thing, running a debug build using ASAN
will give us a lot more information when it does crash. Or you can
run a debug build with gdb, which is a little more cumbersome, but
should get some good crash information for us to work with.
Let me know if you need help setting either of those up. The cmake
line for ASAN is:
cmake .. -DCMAKE_BUILD_TYPE=Debug -DCMAKE_CXX_FLAGS="-Werror -
fsanitize=address -fno-omit-frame-pointer"
It's in the README.md.
Ted.
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
