View Single Post
Old 10-07-2014, 05:03 PM   #120
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,709
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Hi DiapDealer,

If you can make a Debug (instead of Release) build and get a good long backtrace of the crash in gdb or by some other way, I would love to see it.

Thanks,

KevinH
Hey Kevin,

Even with a debug build on Linux, I'm just not getting much insight into the Qt libraries themselves. The binary Qt 5 downloads for Linux don't have separate Release/Debug versions of the libraries like the Windows downloads do ... and I can't seem to figure out how to load (or turn on) the extra debugging symbols for Qt5 itself. I may have to resort to using the Windows debugging tools to get a helpful backtrace. I don't look forward to remembering how to do that.
DiapDealer is online now