From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: lekktu@gmail.com, 16504@debbugs.gnu.org
Subject: bug#16504: 24.3.50; emacs_backtrace.txt
Date: Tue, 21 Jan 2014 08:05:09 -0800 (PST) [thread overview]
Message-ID: <ea589ef7-92ee-4d89-ab16-39d8862c41ac@default> (raw)
In-Reply-To: <<83iotdgx17.fsf@gnu.org>>
> > > Drew, can you please post a couple of backtraces from these frequent
> > > crashes?
> >
> > They are the same backtrace - this bug.
>
> I'm confused: you said that this bug was about specifying an incorrect
> string for a font. If so, the other crashes are most probably caused
> by a different cause.
What I provided in the original report for this bug is a way to reproduce the crash, starting from emacs -Q. It is also how I first encountered the crash (usually, I encounter a crash first in my own setup).
I later added that with my own setup I am frequently getting crashes that produce the same backtrace (exactly). And those appear to be random (do not appear to be associated with anything particular that I am doing at the time of the crash).
I also reported a different backtrace separately as a different bug. But for this bug all of the backtraces have been the same, and the original bug report gives you a way to reproduce it.
HTH.
next parent reply other threads:[~2014-01-21 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<9bfcf9de-9128-4369-a056-5299266ebfe8@default>
[not found] ` <<83iotdgx17.fsf@gnu.org>
2014-01-21 16:05 ` Drew Adams [this message]
2014-01-21 16:27 ` bug#16504: 24.3.50; emacs_backtrace.txt Eli Zaretskii
[not found] <<b3e943f8-65a1-4715-8938-70d1ed4495ea@default>
[not found] ` <<CAAeL0SQWqKohR3ydn2+Tymxcncz6=yxQ2eXy8c4QPQp239pkOA@mail.gmail.com>
[not found] ` <<838uuaipkm.fsf@gnu.org>
[not found] ` <<CAAeL0SQhRerRgZcRb7w3YJBYW82UugCXc6_-uVJxruM4K3wG5g@mail.gmail.com>
[not found] ` <<419a95c9-a5f1-4c57-9e93-ebb8f81cdea8@default>
[not found] ` <<CAAeL0STP01eFV-aWtSvpuU3kcRrMV9jQ2+ZpSf+-e8Y6JL8rpQ@mail.gmail.com>
[not found] ` <<83ppnmgfvp.fsf@gnu.org>
2014-01-21 3:57 ` Drew Adams
2014-01-21 15:44 ` Eli Zaretskii
2014-01-20 8:06 Drew Adams
2014-01-20 8:45 ` Drew Adams
2014-01-20 11:58 ` Juanma Barranquero
2014-01-20 16:27 ` Eli Zaretskii
2014-01-20 12:05 ` Juanma Barranquero
2014-01-20 16:30 ` Eli Zaretskii
2014-01-20 16:33 ` Juanma Barranquero
2014-01-20 19:13 ` Eli Zaretskii
2014-01-20 23:35 ` Juanma Barranquero
2014-01-21 3:40 ` Eli Zaretskii
2014-01-21 15:42 ` Eli Zaretskii
2014-01-20 21:29 ` Drew Adams
2014-01-20 23:36 ` Juanma Barranquero
2014-01-21 3:42 ` Eli Zaretskii
2014-01-21 4:01 ` Juanma Barranquero
2015-12-26 12:55 ` Lars Ingebrigtsen
2016-04-29 15:47 ` Lars Ingebrigtsen
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=ea589ef7-92ee-4d89-ab16-39d8862c41ac@default \
--to=drew.adams@oracle.com \
--cc=16504@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).