While investigating bug 616198, I'm showing a weird crash at live_effects/lpe-bendpath.cpp:108 the uskeleton.cuts variable is either not set or not setup correctly and borks. I couldn't work out exactly what to do since it's not anything I can see.
I'd love to know what's going wrong with this bug to improve my understanding of C++. Any help would be greatly appreciated.
Martin,
On Jun 28, 2013, at 7:23 AM, Martin Owens wrote:
While investigating bug 616198, I'm showing a weird crash at live_effects/lpe-bendpath.cpp:108 the uskeleton.cuts variable is either not set or not setup correctly and borks. I couldn't work out exactly what to do since it's not anything I can see.
I'd love to know what's going wrong with this bug to improve my understanding of C++. Any help would be greatly appreciated.
Martin,
One thing that really helps in cases like these is to run with Valgrind. If it's a matter of some variable being uninitialized, it is very good at catching and reporting such.
On 28-6-2013 16:23, Martin Owens wrote:
While investigating bug 616198, I'm showing a weird crash at live_effects/lpe-bendpath.cpp:108 the uskeleton.cuts variable is either not set or not setup correctly and borks. I couldn't work out exactly what to do since it's not anything I can see.
I'd love to know what's going wrong with this bug to improve my understanding of C++. Any help would be greatly appreciated.
Martin,
See my comments in the bug report and the crash-fix in rev 12398.
Cheers, Johan
On Mon, 2013-07-01 at 23:06 +0200, Johan Engelen wrote:
See my comments in the bug report and the crash-fix in rev 12398.
Thanks for the fix Johan. I'd traced it enough to know that the uskeleton container was being set, but didn't know enough about the calling function.
I'm going to call the bug fixed, because while we may have questions about what to do in such a scenario, the image loads ok and looks ok and the crash doesn't happen.
Martin,
participants (3)
-
Johan Engelen -
Jon Cruz -
Martin Owens