From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <imz@altlinux.org>
Date: Fri, 24 Nov 2017 16:52:17 +0300 (MSK)
From: Ivan Zakharyaschev <imz@altlinux.org>
To: "devel@ where you _can_ ask" <devel-newbies@lists.altlinux.org>
In-Reply-To: <alpine.LFD.2.20.1711241209530.7714@imap.altlinux.org>
Message-ID: <alpine.LFD.2.20.1711241628110.7714@imap.altlinux.org>
References: <20171122094156.GA6595@gyle.altlinux.org>
 <4074666d-60cd-78ec-c956-93249afee32e@basealt.ru>
 <alpine.LFD.2.20.1711241209530.7714@imap.altlinux.org>
User-Agent: Alpine 2.20 (LFD 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed;
 BOUNDARY="1807885841-1807919982-1511531537=:7714"
Cc: grenka@altlinux.org
Subject: Re: [newbies] [#195123] EPERM
 ltrace.git=0.7.91.0.198.git82c6640-alt1
X-BeenThere: devel-newbies@lists.altlinux.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "devel@ where you _can_ ask" <devel-newbies@lists.altlinux.org>
List-Id: "devel@ where you _can_ ask" <devel-newbies.lists.altlinux.org>
List-Unsubscribe: <https://lists.altlinux.org/mailman/options/devel-newbies>, 
 <mailto:devel-newbies-request@lists.altlinux.org?subject=unsubscribe>
List-Archive: <http://lists.altlinux.org/pipermail/devel-newbies>
List-Post: <mailto:devel-newbies@lists.altlinux.org>
List-Help: <mailto:devel-newbies-request@lists.altlinux.org?subject=help>
List-Subscribe: <https://lists.altlinux.org/mailman/listinfo/devel-newbies>,
 <mailto:devel-newbies-request@lists.altlinux.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Nov 2017 13:52:18 -0000
Archived-At: <http://lore.altlinux.org/devel-newbies/alpine.LFD.2.20.1711241628110.7714@imap.altlinux.org/>
List-Archive: <http://lore.altlinux.org/devel-newbies/>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1807885841-1807919982-1511531537=:7714
Content-Type: text/plain; format=flowed; charset=KOI8-R
Content-Transfer-Encoding: 8BIT

Попробовал на своей машине, оно не очень приятно падает в этом режиме:

$ ltrace  -x \* /bin/ls /var/empty/
....
<... check_match resumed> ) 
= { 18799, '\022', '\0', 13, 221008, 220 }
<... do_lookup_x resumed> ) 
= 1
<... _dl_lookup_symbol_x resumed> ) 
= <void>
<... _dl_fixup resumed> ) 
= 140287210082128
getenv@libc.so.6("COLUMNS" <unfinished ...>
strlen@libc.so.6("COLUMNS") 
= 7
<... getenv resumed> ) 
= nil
ioctl( <unfinished ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

$ ltrace  -x \* /bin/echo a
....
<... check_match resumed> ) 
= { 20645, '"', '\0', 13, 471424, 151 }
<... do_lookup_x resumed> ) 
= 1
<... _dl_lookup_symbol_x resumed> ) 
= <void>
<... _dl_fixup resumed> ) 
= 140342807331200
fputs_unlocked@libc.so.6(0x7fffa221149b, 0x7fa400007fa4, 45, 32 
<unfinished ...>
strlen@libc.so.6("a") 
= 1
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

$ rpm -q ltrace coreutils-debuginfo glibc-core-debuginfo
ltrace-0.7.91.0.198.git82c6640-alt1.x86_64
coreutils-debuginfo-8.27.0.23.f4570-alt1.x86_64
glibc-core-debuginfo-2.25-alt3.x86_64
$

Думаю, если это бага upstream-а, то это не препятствие для попадания 
пакета в Sisyphus. Можно будет в bugzill-е зафиксировать её просто.

Без debuginfo то же поведение.

-- 
Best regards,
Ivan

--1807885841-1807919982-1511531537=:7714--