unsubscribe On Mon, Aug 15, 2016 at 4:52 PM, Mert Dirik <[email protected]> wrote:
> On Fri, 10 Jun 2016 02:02:59 -0400 Michael Gilbert <[email protected]> > wrote: > > > How about stack traces from a first message? Are they useless? > > > > Without debugging symbols, basically yes. > > > > > If you want full backtrace from gdb then describe how to get if, > because > > > usual approach (gdb <program> --> run --> segfault --> bt full) will > not > > > work with chromium as far as I understand. > > > > https://wiki.debian.org/AutomaticDebugPackages > > > > Also see "man chromium". > > > > Hopefully I've managed to get a useful stack trace in jessie (though > it still says > no debugging symbols found?) > > 1. Ran with "chromium --temp-profile --debug 'about:blank'" > 2. Program started fine, but crashed as soon as I had clicked the new tab > button > > Attached is a full gdb log with outputs of bt, thread apply all bt, bt > full and thread apply all bt full > commands. >
