From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: building/using address-sanitizer-enabled emacs? Date: Wed, 17 May 2017 07:46:49 -0700 Organization: UCLA Computer Science Department Message-ID: <2fc8d303-8855-fcb9-754d-bc804c3681fe@cs.ucla.edu> References: <83wp9scbwi.fsf@gnu.org> <83shkfct06.fsf@gnu.org> <83fugfcp3b.fsf@gnu.org> <9089f9ef-5312-2d82-a671-b63269a3312b@cs.ucla.edu> <83bmr1bfhj.fsf@gnu.org> <83r2zo5ifv.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1495032437 26121 195.159.176.226 (17 May 2017 14:47:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 17 May 2017 14:47:17 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 Cc: jim@meyering.net, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 17 16:47:10 2017 Return-path: Envelope-to: ged-emacs-devel@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 1dB0EG-0006b2-Os for ged-emacs-devel@m.gmane.org; Wed, 17 May 2017 16:47:08 +0200 Original-Received: from localhost ([::1]:49351 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dB0EM-0000S8-9z for ged-emacs-devel@m.gmane.org; Wed, 17 May 2017 10:47:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49178) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dB0E5-0000LT-Fr for emacs-devel@gnu.org; Wed, 17 May 2017 10:46:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dB0E4-00036d-NC for emacs-devel@gnu.org; Wed, 17 May 2017 10:46:57 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:48654) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dB0E0-00034a-Ux; Wed, 17 May 2017 10:46:53 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 1D3E0160083; Wed, 17 May 2017 07:46:51 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id nwO80_LNHEmr; Wed, 17 May 2017 07:46:50 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 6A3FD160096; Wed, 17 May 2017 07:46:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id I9hnj7_iGmP8; Wed, 17 May 2017 07:46:50 -0700 (PDT) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 0F66C160083; Wed, 17 May 2017 07:46:50 -0700 (PDT) In-Reply-To: <83r2zo5ifv.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214910 Archived-At: On 05/16/2017 07:24 PM, Eli Zaretskii wrote: > isn't it strange that none of the changes you made is > related to starting a sub-process, which was where the original report > came from? Although Jim's original report mentioned process.c, the referenced code was in server_accept_connection (not starting a sub-process), and that code was indeed affected by one of the recent changes I made (commit be9e60fc3c43cc49cc5d749924c3e96737ae297c). Jim's original report mainly focused on a buffer overflow in dumping. That part has never worked with AddressSanitizer; one must configure with CANNOT_DUMP=yes to use AddressSanitizer.