From: Paul Eggert <eggert@cs.ucla.edu>
To: Nicolas Avrutin <nicolasavru@gmail.com>
Cc: 13867@debbugs.gnu.org
Subject: bug#13867: 24.3.50; reading certain emails containing images in mu4e causes segfault
Date: Mon, 04 Mar 2013 20:41:18 -0800 [thread overview]
Message-ID: <5135776E.3070603@cs.ucla.edu> (raw)
In-Reply-To: <87hakri0dk.fsf@gateway.local.navru.net>
To make this easier to reproduce, can you pull the image
in question out of the email, and visit it separately?
If that makes emacs -Q dump core, then we can try to
visit the image ourselves.
You might try a "bzr up", as there was a recent fix for an
ImageMagick core dump in trunk bzr 111937 (see Bug#13846 in
<http://bugs.gnu.org/13846>) and this is later than the
version you built.
Also, can you please try building Emacs without optimization
and with debugging symbols, and generating a backtrace for that?
next prev parent reply other threads:[~2013-03-05 4:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 16:40 bug#13867: 24.3.50; reading certain emails containing images in mu4e causes segfault Nicolas Avrutin
2013-03-05 4:41 ` Paul Eggert [this message]
[not found] ` <877glmpagw.fsf@gateway.local.navru.net>
2013-03-05 8:50 ` Paul Eggert
[not found] ` <87haknyxwa.fsf@gateway.local.navru.net>
2013-03-07 17:48 ` Paul Eggert
2013-03-07 18:11 ` Nicolas Avrutin
2013-03-07 23:20 ` Nicolas Avrutin
2013-03-07 23:53 ` Paul Eggert
2013-03-07 17:57 ` Nicolas Avrutin
2013-03-07 23:52 ` Paul Eggert
2013-03-08 0:16 ` Nicolas Avrutin
2013-03-08 1:13 ` Paul Eggert
2013-03-08 18:02 ` Nicolas Avrutin
2013-03-09 6:19 ` Paul Eggert
2013-03-09 18:54 ` Nicolas Avrutin
2013-03-10 6:36 ` Paul Eggert
2013-03-17 6:46 ` Nicolas Avrutin
2013-03-17 6:58 ` Paul Eggert
2013-03-17 13:06 ` Stefan Monnier
2013-03-18 5:28 ` Paul Eggert
2013-03-18 12:36 ` Nicolas Avrutin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5135776E.3070603@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=13867@debbugs.gnu.org \
--cc=nicolasavru@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.