From: Drew Adams <drew.adams@oracle.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 15994@debbugs.gnu.org
Subject: bug#15994: 24.3.50; emacs_backtrace.txt
Date: Sun, 1 Dec 2013 08:52:53 -0800 (PST) [thread overview]
Message-ID: <e39de0f7-c614-446c-9b3c-29312621621f@default> (raw)
In-Reply-To: <CAH8Pv0jZiZSHBHcw5OkdgQn+vwyLRagbodRXn+R6ieJwwn07MQ@mail.gmail.com>
> On Thu, Nov 28, 2013 at 10:31 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > I am getting this same backtrace all the time now. I can get it from
> > clicking mouse-2 on a candidate in *Completions* (but not always),
> > and I can get it from hitting `C-g' during completion.
> >
> > Quite annoying. The build is pretty much unusable, I'm afraid.
> > I must have had more than 20 crashes with the same backtrace in
> > the last 10 minutes or so. Can't really do anything with this build.
>
> I made that build this morning from a machine (my office desktop PC)
> which is different from the machine I usually employ to make the
> builds (my personal laptop). AFAIK, the build environment is the same
> in both machines, but anyway, to be sure that the problem isn't due to
> a faulty build, please try the last binary I've just made and uploaded
> (this one is made from my laptop, as usual):
> emacs-r115271-20131128-w32-bin.7z.
>
> (BTW, I've also used a different compression format, 7z, but I think
> this should not make a difference)
FWIW - Since I downloaded that second build for 2013-11-28, I have not
noticed crashes. So perhaps the crashes were indeed due to a bad
build from your office PC. I am using only the second build now (from
your laptop), and I haven't noticed crashes. HTH.
next prev parent reply other threads:[~2013-12-01 16:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 21:20 bug#15994: 24.3.50; emacs_backtrace.txt Drew Adams
2013-11-28 21:31 ` Drew Adams
2013-11-28 22:26 ` Dani Moncayo
2013-11-28 22:37 ` Drew Adams
2013-12-01 16:52 ` Drew Adams [this message]
2013-12-01 18:25 ` Drew Adams
2013-12-02 2:00 ` Drew Adams
2013-12-02 17:38 ` Eli Zaretskii
2014-02-10 4:10 ` Lars Ingebrigtsen
2014-02-10 5:23 ` Drew Adams
2014-02-10 5:52 ` Lars Ingebrigtsen
2014-02-10 6:01 ` Drew Adams
2014-02-10 16:40 ` Eli Zaretskii
2013-12-02 2:31 ` Drew Adams
2013-11-29 7:08 ` Eli Zaretskii
2013-11-28 21:33 ` Dani Moncayo
2013-11-28 21:58 ` Drew Adams
2013-11-29 7:06 ` Eli Zaretskii
[not found] <<f5b97008-9878-463f-99c3-9d64e6280ebe@default>
[not found] ` <<83d2lj8z62.fsf@gnu.org>
2013-11-29 8:23 ` Drew Adams
[not found] ` <<b6b1261d-45a0-4d59-87cb-af21bd12f02c@default>
[not found] ` <<83bo138z3d.fsf@gnu.org>
2013-11-29 8:26 ` Drew Adams
[not found] ` <<CAH8Pv0jZiZSHBHcw5OkdgQn+vwyLRagbodRXn+R6ieJwwn07MQ@mail.gmail.com>
[not found] ` <<e39de0f7-c614-446c-9b3c-29312621621f@default>
[not found] ` <<015bf53e-c4c7-4344-a8a4-193dbb7113bc@default>
[not found] ` <<a34bd9c2-d531-4774-837c-90c1b54cdf67@default>
[not found] ` <<8361r75f26.fsf@gnu.org>
2013-12-02 18:19 ` 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=e39de0f7-c614-446c-9b3c-29312621621f@default \
--to=drew.adams@oracle.com \
--cc=15994@debbugs.gnu.org \
--cc=dmoncayo@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).