From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nicolas Richard Newsgroups: gmane.emacs.bugs Subject: bug#17168: 24.3.50; Segfault at mark_object Date: Wed, 02 Apr 2014 19:59:11 +0200 Message-ID: <87vburr4sw.fsf@yahoo.fr> References: <87y4zop44m.fsf@yahoo.fr> <533C3277.30706@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1396524805 8892 80.91.229.3 (3 Apr 2014 11:33:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Apr 2014 11:33:25 +0000 (UTC) Cc: Nicolas Richard , 17168@debbugs.gnu.org To: Daniel Colascione Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Apr 03 13:33:18 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WVeJl-00075K-HQ for geb-bug-gnu-emacs@m.gmane.org; Thu, 03 Apr 2014 11:52:17 +0200 Original-Received: from localhost ([::1]:39996 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVPSX-0005Uw-SN for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Apr 2014 14:00:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54497) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVPSO-0005GN-9U for bug-gnu-emacs@gnu.org; Wed, 02 Apr 2014 14:00:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVPSH-0000a1-Fb for bug-gnu-emacs@gnu.org; Wed, 02 Apr 2014 14:00:12 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:60295) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVPSH-0000Zg-CI for bug-gnu-emacs@gnu.org; Wed, 02 Apr 2014 14:00:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WVPSG-0001Sy-Mc for bug-gnu-emacs@gnu.org; Wed, 02 Apr 2014 14:00:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Nicolas Richard Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 02 Apr 2014 18:00:04 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 17168 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 17168-submit@debbugs.gnu.org id=B17168.13964615555514 (code B ref 17168); Wed, 02 Apr 2014 18:00:04 +0000 Original-Received: (at 17168) by debbugs.gnu.org; 2 Apr 2014 17:59:15 +0000 Original-Received: from localhost ([127.0.0.1]:33240 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WVPRT-0001Qs-D7 for submit@debbugs.gnu.org; Wed, 02 Apr 2014 13:59:15 -0400 Original-Received: from mailrelay008.isp.belgacom.be ([195.238.6.174]:11824) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WVPRR-0001Qh-5b for 17168@debbugs.gnu.org; Wed, 02 Apr 2014 13:59:13 -0400 X-Belgacom-Dynamic: yes Original-Received: from 55.22-200-80.adsl-dyn.isp.belgacom.be (HELO LDLC-portable) ([80.200.22.55]) by relay.skynet.be with ESMTP; 02 Apr 2014 19:59:12 +0200 In-Reply-To: <533C3277.30706@dancol.org> (Daniel Colascione's message of "Wed, 02 Apr 2014 08:53:27 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.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-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:87674 Archived-At: Daniel Colascione writes: > On 04/02/2014 12:44 AM, Nicolas Richard wrote: >> This happened while I was away. > > i686? Linux? mark_vectorlike? Good. This bug sounds like a manifestation > of the GC bug we've been hunting for a while. Would you be comfortable > sharing a core dump next time (perhaps privately)? If not, please > collect a core dump anyway so that we can ask you questions about it. For the record, I sent the core dump privately. I also kept the gdb session open. -- Nico.