From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16234@debbugs.gnu.org
Subject: bug#16234: 24.3.50; emacs_backtrace.txt
Date: Wed, 25 Dec 2013 05:17:18 +0100 [thread overview]
Message-ID: <CAAeL0SQv0cvzX+MCA_S=AGHYOH-mkHeRz2trwTRxvoHo=cRfxg@mail.gmail.com> (raw)
In-Reply-To: <837gau6sky.fsf@gnu.org>
On Tue, Dec 24, 2013 at 6:56 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 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.
next prev parent reply other threads:[~2013-12-25 4:17 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 [this message]
2013-12-25 5:29 ` Drew Adams
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='CAAeL0SQv0cvzX+MCA_S=AGHYOH-mkHeRz2trwTRxvoHo=cRfxg@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=16234@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).