unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 13140@debbugs.gnu.org
Subject: bug#13140: 24.3.50; emacs_backtrace.txt
Date: Thu, 13 Dec 2012 20:53:41 +0100	[thread overview]
Message-ID: <CAH8Pv0hgDYZ0z+AbugyMSju1C74Oz_z73jBHe2d5JZ5c7rUFNA@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0SR649LYjANsutnG904w1ZvWJzt43vOfeg3yCi2ZE8NcpQ@mail.gmail.com>

>> In case this is somehow due to a defect in the build I made [1], it
>> would be good that someone made and upload a build of the current
>> trunk, so that Drew could try it and see if the crashes happen then
>> too.
>
> Drew, if you're interested you can grab a build from today's trunk at
> https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99

Juanma, did you configure with "--enable-checking" ?

I ask this because I configured with it, and IIUC, these backtraces
that Drew is getting are due to assertions which are enabled only if
Emacs was configured with that option.

OTOH, I also passed "--no-opt" to the configure script, which perhaps
might make a difference too.

-- 
Dani Moncayo





  parent reply	other threads:[~2012-12-13 19:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 15:49 bug#13140: 24.3.50; emacs_backtrace.txt Drew Adams
2012-12-11 15:59 ` Eli Zaretskii
2012-12-12  3:10   ` Drew Adams
2012-12-12  3:56     ` Drew Adams
2013-02-23  1:08       ` Glenn Morris
2012-12-12  3:58     ` Eli Zaretskii
2012-12-12  7:31       ` Dani Moncayo
2012-12-12  8:14         ` Glenn Morris
2012-12-12 15:20           ` Juanma Barranquero
2012-12-12 16:18           ` Drew Adams
2012-12-12 18:11         ` Juanma Barranquero
2012-12-12 18:14           ` Drew Adams
2012-12-13 19:53           ` Dani Moncayo [this message]
2012-12-13 20:04             ` Dani Moncayo
2014-02-10  4:47               ` Lars Ingebrigtsen
2012-12-14 10:24             ` martin rudalics

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=CAH8Pv0hgDYZ0z+AbugyMSju1C74Oz_z73jBHe2d5JZ5c7rUFNA@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=13140@debbugs.gnu.org \
    --cc=lekktu@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).