From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: `message' not outputting the newline "atomically" Date: Wed, 26 Jun 2019 18:23:31 +0300 Message-ID: <83tvccjrpo.fsf@gnu.org> References: <07619925-e367-fb88-2dd8-27addb2e9052@grinta.net> <68b398b1-3790-b32f-535d-6ea2518f79b8@cs.ucla.edu> <83pnn1lkej.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="188367"; mail-complaints-to="usenet@blaine.gmane.org" Cc: eggert@cs.ucla.edu, daniele@grinta.net, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 26 17:25:44 2019 Return-path: Envelope-to: ged-emacs-devel@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 1hg9ns-000msP-4B for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2019 17:25:44 +0200 Original-Received: from localhost ([::1]:41094 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hg9nr-0007Kq-5h for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2019 11:25:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42244) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hg9m0-00065D-Qp for emacs-devel@gnu.org; Wed, 26 Jun 2019 11:23:49 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54077) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hg9m0-00032m-AX; Wed, 26 Jun 2019 11:23:48 -0400 Original-Received: from [176.228.60.248] (port=3100 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hg9lz-0000xk-Ni; Wed, 26 Jun 2019 11:23:48 -0400 In-reply-to: (message from Lars Ingebrigtsen on Wed, 26 Jun 2019 11:21:43 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:238163 Archived-At: > From: Lars Ingebrigtsen > Cc: Paul Eggert , daniele@grinta.net, emacs-devel@gnu.org > Date: Wed, 26 Jun 2019 11:21:43 +0200 > > Eli Zaretskii writes: > > > It is very unusual for code_convert_string to allocate memory; > > normally it just reuses a buffer that was allocated at startup. > > Hm! How does that work? Is that a buffer that's used for all strings > Emacs allocates or something? I tried to follow the code, and we seem > to end up in allocate_string_data, which calls malloc... Sorry, I've probably misunderstood what was being discussed. I thought you were talking about the conversion itself. The target string is of course created via xmalloc. B ut that could hardly infloop.