GNU bug report logs - #22058
25.1.50; emacs_backtrace.txt

Previous Next

Full log

Message #45 received at 22058 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: jwiegley <at> gmail.com, 22058 <at> debbugs.gnu.org, lekktu <at> gmail.com
Subject: Re: bug#22058: 25.1.50; emacs_backtrace.txt
Date: Tue, 01 Dec 2015 17:26:18 +0200

> Date: Mon, 30 Nov 2015 19:51:03 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: 22058 <at> debbugs.gnu.org
> 
> > > Drew's binaries are compiled with -O0 -ggdb3 (or lately,
> > > -Og -ggdb3) and non-stripped.
> > 
> > If that's the case, Drew, can you run using:
> >     gdb --args emacs <args to Emacs>
> > And then use it until it crashes again?  That should give
> > us a better trace.
> 
> If that gives you a better trace, and that's all you're
> asking, I may give it a try.

That alone will produce important information about the problem.

> Or are you also asking me to keep it open with gdb after
> it crashes and fiddle with gdb to debug it?

That'd be nice.  Failing that, typing these 2 GDB commands when Emacs
crashes:

  (gdb) thread 1
  (gdb) bt

(without the "(gdb)" part -- this is the GDB prompt) should tell us
something useful.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.