unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juanma Barranquero <lekktu@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 16234@debbugs.gnu.org
Subject: bug#16234: 24.3.50; emacs_backtrace.txt
Date: Tue, 24 Dec 2013 21:29:22 -0800 (PST)	[thread overview]
Message-ID: <06250503-b722-49ee-8d35-af1b8ca34107@default> (raw)
In-Reply-To: <CAAeL0SQv0cvzX+MCA_S=AGHYOH-mkHeRz2trwTRxvoHo=cRfxg@mail.gmail.com>

> > Aha! the trap worked!  I installed in trunk revision something that
> > will hopefully show us a full backtrace from intervals.c:679, so we
> > could try to find out whodunit.
> 
> emacs-20131225-r115738-bin-i386.zip is on its way to Dropbox.

Thanks.  I picked it up and tried it.  But as I said earlier, I'm
afraid the crash was fortuitous, not something I can easily reproduce.
As I mentioned, I had already used M-k in the minibuffer more than
once, even for the same command invocation.  Only once did the crash
occur when I did that.

So far, I have not gotten a crash.  Will of course let you know.


[However, something else (horrible) must have changed in this build,
because now when I use my (own) command to open a file, it takes
multiple seconds just to calculate the list of candidate files in my
usual directory.  Nothing to do with the problem at hand.  But it
does mean that this build is not something I can use, to do more
than test for this bug and hope for another crash.]





      reply	other threads:[~2013-12-25  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  4:23 bug#16234: 24.3.50; emacs_backtrace.txt Drew Adams
2013-12-24  4:39 ` Juanma Barranquero
2013-12-24 17:56   ` Eli Zaretskii
2013-12-25  4:17     ` Juanma Barranquero
2013-12-25  5:29       ` Drew Adams [this message]

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=06250503-b722-49ee-8d35-af1b8ca34107@default \
    --to=drew.adams@oracle.com \
    --cc=16234@debbugs.gnu.org \
    --cc=eliz@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).