From: Eric Hanchrow <eric.hanchrow@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22120@debbugs.gnu.org
Subject: bug#22120: Another backtrace
Date: Thu, 10 Dec 2015 19:15:52 +0000 [thread overview]
Message-ID: <CAHZoxq_n8eg-YKC044sMxOrqP43b_3Q4h2FDMgF7kGcTGEgYNQ@mail.gmail.com> (raw)
In-Reply-To: <83bn9y9lfd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Thu, Dec 10, 2015 at 11:02 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > 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?
I was under the impression that this build _was_ unoptimized (so I was
surprised to see those variables "optimized out"). I configured with
$ ./configure --enable-checking --enable-check-lisp-object-type
--config-cache CFLAGS=-Og -g3
Maybe I should add -O0 to CFLAGS. (I got those options from a recent
thread on emacs-devel about a proposed new file etc/DEBUG).
> Also, it looks like you configured with --enable-check-lisp-object-type,
> is that right?
Yes.
> 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.
>
Oho! OK.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1840 bytes --]
next prev parent reply other threads:[~2015-12-10 19:15 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
2015-12-10 19:15 ` Eric Hanchrow [this message]
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=CAHZoxq_n8eg-YKC044sMxOrqP43b_3Q4h2FDMgF7kGcTGEgYNQ@mail.gmail.com \
--to=eric.hanchrow@gmail.com \
--cc=22120@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).