From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1B7CE431FB6 for ; Sun, 17 Aug 2014 11:40:41 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNvvhpiVZayI for ; Sun, 17 Aug 2014 11:40:33 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 67416431FAE for ; Sun, 17 Aug 2014 11:40:33 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1XJ5NM-00050Y-T3; Sun, 17 Aug 2014 15:40:20 -0300 Received: (nullmailer pid 9703 invoked by uid 1000); Sun, 17 Aug 2014 18:40:16 -0000 From: David Bremner To: sfischme@uwaterloo.ca, notmuch@notmuchmail.org Subject: Re: SVG attachment crashes emacs In-Reply-To: <8738cvck2g.fsf@uwaterloo.ca> References: <8738cvck2g.fsf@uwaterloo.ca> User-Agent: Notmuch/0.18.1 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sun, 17 Aug 2014 11:40:16 -0700 Message-ID: <87tx5b7yen.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2014 18:40:41 -0000 Sebastian Fischmeister writes: > Hi, > > When I receive an SVG attachment, it first makes emacs freeze and then > crash. It might not be a problem of notmuch but a helper application, > but I don't know how to debug it; so maybe someone here can help me. > Hi Sebastian; Can you send a sample message, perhaps as an attachement so we can try to duplicate the problem? So far these things are usually upstream emacs bugs, but they do get fixed if we make a good bug report. d