From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#36431: Crash in marker.c:337 Date: Sun, 30 Jun 2019 17:52:13 +0300 Message-ID: <83ef3bf7mq.fsf@gnu.org> References: <831rzch9nd.fsf@gnu.org> <83zhm0fuqg.fsf@gnu.org> <20190630.092626.1377512789964814286.wl@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="65157"; mail-complaints-to="usenet@blaine.gmane.org" Cc: monnier@iro.umontreal.ca, 36431@debbugs.gnu.org To: Werner LEMBERG Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Jun 30 16:53:09 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hhbCW-000Gpj-E7 for geb-bug-gnu-emacs@m.gmane.org; Sun, 30 Jun 2019 16:53:08 +0200 Original-Received: from localhost ([::1]:45008 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hhbCV-0001RX-FA for geb-bug-gnu-emacs@m.gmane.org; Sun, 30 Jun 2019 10:53:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58813) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hhbCQ-0001RD-Ot for bug-gnu-emacs@gnu.org; Sun, 30 Jun 2019 10:53:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hhbCP-00042c-SF for bug-gnu-emacs@gnu.org; Sun, 30 Jun 2019 10:53:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33542) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hhbCP-00042U-Oc for bug-gnu-emacs@gnu.org; Sun, 30 Jun 2019 10:53:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hhbCP-0005Hr-Ly for bug-gnu-emacs@gnu.org; Sun, 30 Jun 2019 10:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 30 Jun 2019 14:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36431 X-GNU-PR-Package: emacs Original-Received: via spool by 36431-submit@debbugs.gnu.org id=B36431.156190634920278 (code B ref 36431); Sun, 30 Jun 2019 14:53:01 +0000 Original-Received: (at 36431) by debbugs.gnu.org; 30 Jun 2019 14:52:29 +0000 Original-Received: from localhost ([127.0.0.1]:47086 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hhbBs-0005H0-Jn for submit@debbugs.gnu.org; Sun, 30 Jun 2019 10:52:28 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:52855) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hhbBq-0005Go-E8 for 36431@debbugs.gnu.org; Sun, 30 Jun 2019 10:52:26 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34696) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hhbBl-0003Jx-7A; Sun, 30 Jun 2019 10:52:21 -0400 Original-Received: from [176.228.60.248] (port=3994 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hhbBk-00079m-Jw; Sun, 30 Jun 2019 10:52:21 -0400 In-reply-to: <20190630.092626.1377512789964814286.wl@gnu.org> (message from Werner LEMBERG on Sun, 30 Jun 2019 09:26:26 +0200 (CEST)) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:161885 Archived-At: > Date: Sun, 30 Jun 2019 09:26:26 +0200 (CEST) > Cc: eliz@gnu.org, 36431@debbugs.gnu.org > From: Werner LEMBERG > > My problem is that I have no idea how to reproduce the problem without > mew. What approach do you suggest? >From the backtrace, I see that the chain of calls is this: "insert-file-contents" (0xffff8ff8) "apply" (0xffff8ff0) "mew-insert-file-contents2" (0xffff95e8) "apply" (0xffff95e0) "mew-insert-file-contents" (0xffff9a40) "mew-encode-mime-body" (0xffffa250) "mew-encode-singlepart" (0xffffa830) "mew-encode-multipart" (0xffffadb0) "mew-encode-make-multi" (0xffffb2f0) "mew-smtp-encode-message" (0xffffb870) "mew-smtp-encode" (0xffffbd40) "mew-draft-smtp-process-message" (0xffffc2a0) "mew-draft-process-message" (0xffffc790) "mew-draft-send-message" (0xffffce80) So my suggestion would be to try to find out what should be the buffer contents before the call to insert-file-contents, and what should be in the file being inserted, to reproduce the problem, and then post the data needed for the reproduction. If you cannot figure this out on the level of insert-file-contents, try going up the call stack, and find the lowest level where you can figure out the arguments and their values, including the contents of any files needed for the reproduction. Then show the results, and we will try to use the relevant mew code to fill in the blanks. One caveat: your mew customizations might be part of the puzzle, so be sure to spell them out. Thanks.