unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Hanchrow <eric.hanchrow@gmail.com>
Cc: 22120@debbugs.gnu.org
Subject: bug#22120: Another backtrace
Date: Thu, 10 Dec 2015 21:02:30 +0200	[thread overview]
Message-ID: <83bn9y9lfd.fsf@gnu.org> (raw)
In-Reply-To: <CAHZoxq8fu0ir6UE6x_WVFvvTfivJokM4kydtzn-0AweE_xJ+Sw@mail.gmail.com>

> From: Eric Hanchrow <eric.hanchrow@gmail.com>
> Date: Thu, 10 Dec 2015 18:42:19 +0000
> 
> What little I could get of the variables' values is at the bottom.

It doesn't tell much.

Can you try reproducing this in an unoptimized build?  It's very hard
to debug optimized code when we suspect some more or less random
corruption of values.  If the problem happens in an unoptimized build,
we won't need to look so hard for bad values.

Also, it looks like you configured with --enable-check-lisp-object-type,
is that right?  If so, please configure without it, that would allow
to see many values directly in the backtrace, instead of asking you to
print them in GDB.

Thanks.





  reply	other threads:[~2015-12-10 19:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 20:19 bug#22120: 25.1.50; segfault while running circe Eric Hanchrow
2015-12-08 20:33 ` Eli Zaretskii
2015-12-08 20:36   ` Eric Hanchrow
2015-12-08 20:54     ` Eli Zaretskii
2015-12-08 21:03       ` John Wiegley
2015-12-09 15:29         ` Eric Hanchrow
     [not found]           ` <83h9jrbl7b.fsf@gnu.org>
2015-12-09 19:13             ` Eric Hanchrow
2015-12-08 20:36 ` John Wiegley
2015-12-08 20:38   ` Eric Hanchrow
2015-12-10 18:42 ` bug#22120: Another backtrace Eric Hanchrow
2015-12-10 19:02   ` Eli Zaretskii [this message]
2015-12-10 19:15     ` Eric Hanchrow
2015-12-10 19:30       ` Eli Zaretskii
2015-12-12 22:37 ` Eric Hanchrow
2015-12-13 15:27   ` Eli Zaretskii
2015-12-13 17:54     ` Eric Hanchrow
2015-12-13 18:04       ` Eli Zaretskii
2015-12-13 18:07         ` Eric Hanchrow
2015-12-13 18:13           ` Eli Zaretskii
2015-12-13 18:19             ` Eric Hanchrow
2015-12-13 18:22               ` Eli Zaretskii
2015-12-13 18:29                 ` Eric Hanchrow
2015-12-24  3:24     ` Eric Hanchrow
2015-12-24 16:12       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bn9y9lfd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22120@debbugs.gnu.org \
    --cc=eric.hanchrow@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).