From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#29031: 25.3; Segmentation fault when starting emacs with my config Date: Tue, 07 Nov 2017 08:55:37 -0500 Message-ID: <874lq65h2e.fsf@users.sourceforge.net> References: <83mv48trbs.fsf@gnu.org> <83bmkotnvm.fsf@gnu.org> <83shdzrrma.fsf@gnu.org> <877ev25idc.fsf@users.sourceforge.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1510063073 4608 195.159.176.226 (7 Nov 2017 13:57:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 7 Nov 2017 13:57:53 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) Cc: 29031@debbugs.gnu.org, monnier@iro.umontreal.ca To: Kaushal Modi Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 07 14:57:47 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eC4Nq-0000la-AB for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Nov 2017 14:57:42 +0100 Original-Received: from localhost ([::1]:53577 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eC4Nx-0007vQ-KB for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Nov 2017 08:57:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43195) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eC4MJ-00076C-R4 for bug-gnu-emacs@gnu.org; Tue, 07 Nov 2017 08:56:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eC4ME-0001NO-6N for bug-gnu-emacs@gnu.org; Tue, 07 Nov 2017 08:56:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:46678) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eC4ME-0001MO-2m for bug-gnu-emacs@gnu.org; Tue, 07 Nov 2017 08:56:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eC4MD-0001tL-Ie for bug-gnu-emacs@gnu.org; Tue, 07 Nov 2017 08:56:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 07 Nov 2017 13:56: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: Original-Received: via spool by 29031-submit@debbugs.gnu.org id=B29031.15100629477242 (code B ref 29031); Tue, 07 Nov 2017 13:56:01 +0000 Original-Received: (at 29031) by debbugs.gnu.org; 7 Nov 2017 13:55:47 +0000 Original-Received: from localhost ([127.0.0.1]:55359 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eC4Lz-0001sk-3l for submit@debbugs.gnu.org; Tue, 07 Nov 2017 08:55:47 -0500 Original-Received: from mail-it0-f50.google.com ([209.85.214.50]:48117) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eC4Lx-0001sX-Jy for 29031@debbugs.gnu.org; Tue, 07 Nov 2017 08:55:46 -0500 Original-Received: by mail-it0-f50.google.com with SMTP id p138so2483427itp.2 for <29031@debbugs.gnu.org>; Tue, 07 Nov 2017 05:55:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=97IOdrH6Qw8WzlgrS+rhi0HzSW+Vs0ezYaVn/nv9+6k=; b=X+fR8F9JLqUhFMI9qp/JFj8CP3oHUAdnUaey1LcumNAATP6KnAk24vKqrIZcs995JF lJH/QHsq+vVhlWPZ3hXUhDvCuloEvt8Yk7+yyGobTMaeh7pmwKABqduEQ1euc+iCL18m ju8dwDXVi00ZJ5amROq3Jx12CdMkvRBjWBRcHB4lSuNbmxdY+YuPHWt0ymCEVPrdMFV5 lRV6ZZzMS2Y1XcZplPSJYhQ0ZYGuOPgLDruNu6oja/waudVctCwUMhSCzSjUn3I7howX hdpPTjVrws62c808s3EdwpFswCNICuhA69foEhMBg7zP6ZvMdnCuMwJUQRCTvH++OKHI Hbpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version :content-transfer-encoding; bh=97IOdrH6Qw8WzlgrS+rhi0HzSW+Vs0ezYaVn/nv9+6k=; b=AvZ47wfPu0ic956KiMKCFl414n6UB1snc6qW4FMXq2TeVWgAO8sqPkTKigLcfvUox2 wxKzu+NMYC5o4VOxohz8+CnamkllOkIz4ZvXJWTNH12qWvBVDc/kFeoerxxDlHfDI8t4 XizOdCjlJ/UwR3wG6Nn8p8psu7ez7NyJUPzSxsC7BWydYt8rUsXt+LJpC7qoPNWjtFWQ 6r/wOU0y0aNBTVEZc1Snit3Do+uxshgTfXe21VFH23NWtq/Lw/JtC/AsMvmaOzN9RJnp NO5UJHM2vNcPuxTxuiVhh24bGYmv/KLCO9Pof1GpmTY5+GQaDqVzvtPiB3U2Kn62HGRW GnFw== X-Gm-Message-State: AJaThX6X0qdjcqWTl3IRr6R2UN7224/E9dv+efhoYmT2mcH5SQMuiRmv pCzlFS5Ndv4n69C1IteRq78= X-Google-Smtp-Source: ABhQp+TBo0dx3TjJbN3y55xoGLLkps6IEnxqxhg+GTaH70JnSnLbY144qtmvxxzn0Hq2iEYQ555NLw== X-Received: by 10.36.0.207 with SMTP id 198mr2202500ita.128.1510062939798; Tue, 07 Nov 2017 05:55:39 -0800 (PST) Original-Received: from zebian ([45.2.119.34]) by smtp.googlemail.com with ESMTPSA id e89sm6562472itd.3.2017.11.07.05.55.37 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 07 Nov 2017 05:55:38 -0800 (PST) In-Reply-To: (Kaushal Modi's message of "Tue, 07 Nov 2017 13:30:35 +0000") 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: 208.118.235.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:139561 Archived-At: 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.=C2=A0 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.