I wouldn't say that debug builds are unusable for bugs like this https://developer.blender.org/T44367 and it would give us a pretty good idea what's happening. Agree though that release with debug symbols will be more useful here. Will need to try if we have stacktrace correctly available there but I expect we will. Debug builds are also how mozilla handles this, see https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_with_WinDbg
On 16 April 2015 at 20:12, Sergey Sharybin <[email protected]> wrote: > I\ve got doubts debug builds will be really useful -- they're really slow > and unusable for investigating th issue. If we do this, it's better to do > something like RelWithDebInfo, but we don't have it in scons. > > So if debug builds are really needed then we'd better to either add such > type of build to scons or use cmake for it. Not sure if cmake is ready for > this, but Martijn knows better. > > There was also some work done related on improving debug backtrace on > windows (afair Alex was working on this). Maybe that'd be more convenient > than requiring to download debug builds for bug reporting? > > On Thu, Apr 16, 2015 at 11:01 PM, Antony Riakiotakis <[email protected]> > wrote: > >> Hi all, >> >> Recently I committed some code that prints a backtrace when Windows >> builds of blender crash. >> >> I've mentioned this countless times already on the tracker, but not >> sure how many people watch the tracker, so I will report it here as >> well: >> >> The windows backtrace does -not- work on release builds. It does work >> on debug builds though. >> >> People have been overeager to include this backtrace in their reports >> so I have promptly disabled >> it on master. >> >> The handler is not useless and it might be nice to make a debug build >> available on our buildbot. >> This will allow us to quickly direct users to a debug build for a >> proper backtrace. >> >> But for now, please dismiss any information in the backtrace as >> garbage (In recent builds it even includes an explicit message so >> people are not confused any more) >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> > > > > -- > With best regards, Sergey Sharybin > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
