From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#29031: 25.3; Segmentation fault when starting emacs with my config Date: Sat, 28 Sep 2019 20:58:33 -0400 Message-ID: <87impb9ava.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="243105"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cc: 29031@debbugs.gnu.org, Stefan Monnier , Kaushal Modi To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Sep 29 02:59:23 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 1iENYY-00118h-Kq for geb-bug-gnu-emacs@m.gmane.org; Sun, 29 Sep 2019 02:59:22 +0200 Original-Received: from localhost ([::1]:35686 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iENYX-00083d-D3 for geb-bug-gnu-emacs@m.gmane.org; Sat, 28 Sep 2019 20:59:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51421) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iENYH-00083R-6H for bug-gnu-emacs@gnu.org; Sat, 28 Sep 2019 20:59:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iENYE-0007KW-3D for bug-gnu-emacs@gnu.org; Sat, 28 Sep 2019 20:59:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42834) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iENYD-0007Jw-QG for bug-gnu-emacs@gnu.org; Sat, 28 Sep 2019 20:59:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iENYD-0005RH-Mx for bug-gnu-emacs@gnu.org; Sat, 28 Sep 2019 20:59:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 29 Sep 2019 00:59:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 29031 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 29031-submit@debbugs.gnu.org id=B29031.156971872220876 (code B ref 29031); Sun, 29 Sep 2019 00:59:01 +0000 Original-Received: (at 29031) by debbugs.gnu.org; 29 Sep 2019 00:58:42 +0000 Original-Received: from localhost ([127.0.0.1]:51655 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iENXt-0005Qe-Ma for submit@debbugs.gnu.org; Sat, 28 Sep 2019 20:58:41 -0400 Original-Received: from mail-io1-f50.google.com ([209.85.166.50]:40914) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iENXs-0005QR-3B for 29031@debbugs.gnu.org; Sat, 28 Sep 2019 20:58:40 -0400 Original-Received: by mail-io1-f50.google.com with SMTP id h144so27896086iof.7 for <29031@debbugs.gnu.org>; Sat, 28 Sep 2019 17:58:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=cgZ2zz6KpeC3PHCkc7goyod5hOJ2VBJVOwO/APEhAdQ=; b=ArY54e4ZeT2bRpofNoUPkkGAR7bNtRs9DNIaZPk7RfF7JKz3lAh6cjzTNJZCWzv6Hg A0s4ydyR7kko8rbn8jbXGJMXpJZZWywYd6NNfSiv3nFUeCKiTt6oKblcvXmWpvNjOO6y SSbafIrpchr/98wh8Hzkjc7Xurb7OAaZ58cO55vtaGM4pbNvKUWWwTM21LWZy4O++rly A1S0HmhjiLch+WaAJ0Wo8cXTPlXP4Px/gJlCeIEadb3aYHPW1mITf/o2S1nPSHAGfnH6 E9KQGhFu62WoDufc30UD66FWBthEggAOE2YaU49SS/ZqzqcTLALK+okvg/AfdCXDGAgJ hlDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=cgZ2zz6KpeC3PHCkc7goyod5hOJ2VBJVOwO/APEhAdQ=; b=M3/jUn+QtRq5/ztBynpUgknI5Yfka15/h5nivDyOhwccc0nya4kKtpkmymr/lYiMGT AxyZbhRAxLZf2n8jopFRMe0Bwj1lpkPzY9HVLHz1ZOIIePmtTJkejMqUxxfexEjjDN48 YHrD1NlIlGWysxrk3nSY1oiIJq9ybnirqJiPqoMgQMPoE81SwCgDiYeVdb4ILw6MX85H nXF266OKm/T6G3l2Ma51K32TdfwdsY0JYqdfOngn/iejv52zAF09WpgcNgySPt5Z3+2j v1QNR/22MT0KM63wmlFiO9UNni8SfmQoMww6Qo7mkPEX5xtdC76DEtGiQRa3ASuaPlLW mGhQ== X-Gm-Message-State: APjAAAWyj86jRsFyROLsTHwn/P4DEfhyVZfVjQjyp+Y0wDfTCszMKPJi GxbxP3bLhrHdVd9EzIMWKzw= X-Google-Smtp-Source: APXvYqzVuXqAYFMMkr3EVbdMBajn6le5d5GJtfV9iggA+4AZTXeZcH+2VFvGU+CA8eNrv6ezqMZ40A== X-Received: by 2002:a5e:a812:: with SMTP id c18mr14775486ioa.220.1569718714642; Sat, 28 Sep 2019 17:58:34 -0700 (PDT) Original-Received: from minid (cbl-45-2-119-34.yyz.frontiernetworks.ca. [45.2.119.34]) by smtp.gmail.com with ESMTPSA id q77sm3411006ill.41.2019.09.28.17.58.33 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 28 Sep 2019 17:58:34 -0700 (PDT) In-Reply-To: (Stefan Kangas's message of "Sun, 29 Sep 2019 02:44:57 +0200") 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:167558 Archived-At: Stefan Kangas writes: > >> Kaushal Modi writes: >> >>> I have no idea what that is. I am not a C developer. So I haven't yet >>> found time to learn valgrind. I read the referenced DEBUG file, but >>> it made no sense. I believe it's a steep learning curve for someone >>> who doesn't know what valgrind is. >> >> Could you try just installing valgrind, reconfiguring and recompile >> emacs with --enable-checking (reconfigure after installing valgrind, as >> configure checks for its header file) and then running 'valgrind emacs' >> and posting the result. I tried this now without making any more >> complex changes suggested in DEBUG and emacs did manage to run. There >> were a couple of warnings about pselect and writev, but otherwise it >> seemed to work okay. >> >> It's possible something useful will come out. If not, we can consider >> whether it's worth trying the more complex stuff. > > Are you still seeing this? If the answer is yes, it seems like more > information is needed here to progress. Could you please try the > procedure suggested above by Noam Postavsky on Emacs 26.3? It would likely be more productive to do this on a version from master, since I believe the switch to pdumper solves some potential problems when using valgrind.