From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f196.google.com (mail-lj1-f196.google.com [209.85.208.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 55A4C4696C3 for ; Fri, 10 Apr 2020 14:50:03 +0300 (MSK) Received: by mail-lj1-f196.google.com with SMTP id t17so1671410ljc.12 for ; Fri, 10 Apr 2020 04:50:03 -0700 (PDT) Date: Fri, 10 Apr 2020 14:50:00 +0300 From: Cyrill Gorcunov Message-ID: <20200410115000.GS3072@uranus> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 13/13] popen: use of exception safe functions for IO List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko Cc: tarantool-patches@dev.tarantool.org On Fri, Apr 10, 2020 at 05:50:51AM +0300, Alexander Turenko wrote: > popen read / write functions provides are written in C and intended to > be used from C: the contract is to return -1 at failure and set an entry > to the diagnostics area. However a C++ exception from coio read / write > functions would pass over a popen function stack frame. > > The solution is to use the recently introduced coio exception safe > functions. > > Part of #4031 Acked-by: Cyrill Gorcunov