On Tue, 23 Feb 2016 16:09:11 -0500 Patrick Shanahan <p...@wahoo.no-ip.org> wrote:
> * J. Paul Bissonnette <jpaulb...@gmail.com> [02-23-16 15:50]: > [...] > > How do I go about the backtracing? > > disclaimer: Definitely Not an Expert! > and this may not help in your instance. > > <from aged memory possibly influenced by Dos Equis> > I am on openSUSE Tumbleweed and I installed (may not be inclusive): > gdb > darktable > darktable-debuginfo > glib-debuginfo > glibc-debuginfo > glib-debugsource > gtk-debugsource > gtk-debuginfo > liblua5_2-debuginfo > > run: gdb darktable > in an xterm: > (gdb) r > > when darktable crashes > (gdb) set pagination off > (gdb) set logging file gdb.txt > (gdb) set logging on > (gdb) thread apply all bt full > > notify the dev's where to see the backtrace, photos and xmp files and > conditions which lead to the crash. > Shortly after I read your post I started Darktable and the problem started. Where do I send the backtrace and file? Paul ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
