From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Dumper issue, revisited; invalid realloc/free Date: Wed, 04 Feb 2015 21:54:38 +0200 Message-ID: <83iofhfo5d.fsf@gnu.org> References: <20150204175709.GX23507@brightrain.aerifal.cx> <83oap9fppc.fsf@gnu.org> <20150204193732.GZ23507@brightrain.aerifal.cx> <83k2zxfomm.fsf@gnu.org> <20150204194910.GA23507@brightrain.aerifal.cx> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1423079722 10629 80.91.229.3 (4 Feb 2015 19:55:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 4 Feb 2015 19:55:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Rich Felker Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 04 20:55:18 2015 Return-path: Envelope-to: ged-emacs-devel@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 1YJ62g-0005yT-0Z for ged-emacs-devel@m.gmane.org; Wed, 04 Feb 2015 20:55:18 +0100 Original-Received: from localhost ([::1]:38484 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ62f-0005Bk-H9 for ged-emacs-devel@m.gmane.org; Wed, 04 Feb 2015 14:55:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57062) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ62F-00054x-O5 for emacs-devel@gnu.org; Wed, 04 Feb 2015 14:54:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YJ62A-00048a-Mw for emacs-devel@gnu.org; Wed, 04 Feb 2015 14:54:51 -0500 Original-Received: from mtaout28.012.net.il ([80.179.55.184]:56423) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ62A-00045q-FT for emacs-devel@gnu.org; Wed, 04 Feb 2015 14:54:46 -0500 Original-Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NJ900500J35SZ00@mtaout28.012.net.il> for emacs-devel@gnu.org; Wed, 04 Feb 2015 21:52:58 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NJ900MNUJ8ASW70@mtaout28.012.net.il>; Wed, 04 Feb 2015 21:52:58 +0200 (IST) In-reply-to: <20150204194910.GA23507@brightrain.aerifal.cx> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.184 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:182397 Archived-At: > Date: Wed, 4 Feb 2015 14:49:10 -0500 > From: Rich Felker > Cc: emacs-devel@gnu.org > > > > > Or that the libc memory allocation routines can gracefully handle > > > > these situations. > > > > > > I would not consider that "graceful". If they detect that the pointer > > > passed to realloc or free is invalid, the only reasonable behavior is > > > to abort. > > > > They could do exactly what you planned to do: ignore the 'free' part > > and only allocate a new block. > > This behavior does not make sense in system malloc Of course, it does: to support Emacs. glibc is still a GNU project, isn't it?