Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14798

Re: [mapfile]: problem reentrance with normal file

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Didou Serge <serge.didou@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: [mapfile]: problem reentrance with normal file
Date Mon, 12 Nov 2018 17:00:09 +0100
Lines 101
Approved bug-bash@gnu.org
Message-ID <mailman.3924.1542038438.1284.bug-bash@gnu.org> (permalink)
References <CACXkx7VreuDnWv8EWvCAiU0E09RRMSgXkabFP5UkBPSgzcVGRA@mail.gmail.com> <cdc5932c-847e-1e55-5785-4e01e2833570@case.edu> <CACXkx7WFFO8nK=H6aKYjVdthgwM_q0p916cJnjLV11FRnoMDEA@mail.gmail.com>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset="UTF-8"
Content-Transfer-Encoding quoted-printable
X-Trace usenet.stanford.edu 1542038438 26409 208.118.235.17 (12 Nov 2018 16:00:38 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-bash@gnu.org, bash@packages.debian.org
To chet.ramey@case.edu
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eQE4cAZp+29N681R1uPxnGTTEiPtZ5cH2R88AwEg5Ic=; b=t9TmvRpIjx0RyjpS2Y9bJzQRlj8BxKJNbi4DHk5qHxLlQ7lEHQoRWcW8hX/atKIMeL TIYw0SaZxB6C7NKVvn/AGUTKY2gYNtrOZZjFgT/W9MBh3uzfNDAhmc4ssj3PrIAU4kvW +Uorx9NmM1dQwLbPl/1LXN39uPEp7V+iWGwUS1DNqvGEtXmXSpCEqpGNsuFoHXRn5uCL YnlutvDc9RYu6W+xtLIxMHMx6coaPuJaWSKhupbfjizrfJXfFIFR/A+qtfNenYJIYmqZ zdOVZqPvdscifk/8eYTBvpcQ1TKnr8SA+uoab7WiNlMb890DLGOi0eAkCasMsjVzgObf r2BA==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eQE4cAZp+29N681R1uPxnGTTEiPtZ5cH2R88AwEg5Ic=; b=UtadoXXbUXedEXJugS6LYg6SAxMv8UUDIOUWBQ6nWxueauNHKtKfWm0o4ffrZTC9Bc X+d4fTzrX227dVPkpyJB9uQDDDUVA2EouX1WjZCt8n2R6WxS0pZUSaj/XND8wK/ic9AN 1ua3cBBOw5RVe8w7VpbaF0twb3l+sFBfiaGugmb56YvyJPOak4z610/C9BxrlcUDB2ar PNZKxddPL8ylYwnc6JptsvWQgxLNpKzz0quxtoId7naRfIz6lnZhC2kmTlO6k5MCIhh/ YEmGwaVAjbfYHXeQNcv/RC3CB4GTGq9tTcC7qbu2C0gqrv0Wx4WQKPW1XfTqfFvE25rk YwMA==
X-Gm-Message-State AGRZ1gKRCWNi3bql3n9F1JUVI3VG+C1+Rvt1CmWa0rWYqCFebPjBWIYY GSafEa9yn6LP7Yluf6AtXM0BSwkV1BE85KwakeU=
X-Google-Smtp-Source AJdET5f6lD21v0grWwZIkJhyKKkkKpkFpVo05vh/OsCxNVcJIzcmyMcJAnRNUhXXXTyPl+IkxUXeFwfQCJyRWTfikxU=
X-Received by 2002:a17:906:e211:: with SMTP id gf17-v6mr9683539ejb.46.1542038421055; Mon, 12 Nov 2018 08:00:21 -0800 (PST)
In-Reply-To <CACXkx7WFFO8nK=H6aKYjVdthgwM_q0p916cJnjLV11FRnoMDEA@mail.gmail.com>
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 2a00:1450:4864:20::542
X-Content-Filtered-By Mailman/MimeDel 2.1.21
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.21
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <http://lists.gnu.org/archive/html/bug-bash/>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref csiph.com gnu.bash.bug:14798

Show key headers only | View raw


I tested with another configuration and ALL work fine:
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -DRECYCLES_PIDS   -I.
-I/usr/src/bash-4.4.12-3.x86_64/src/bash-4.4
-I/usr/src/bash-4.4.12-3.x86_64/src/bash-4.4/include
-I/usr/src/bash-4.4.12-3.x86_64/src/bash-4.4/lib  -DWORDEXP_OPTION -ggdb
-O2 -pipe -Wimplicit-function-declaration
-fdebug-prefix-map=/usr/src/bash-4.4.12-3.x86_64/build=/usr/src/debug/bash-4.4.12-3
-fdebug-prefix-map=/usr/src/bash-4.4.12-3.x86_64/src/bash-4.4=/usr/src/debug/bash-4.4.12-3
-Wno-parentheses -Wno-format-security
uname output: CYGWIN_NT-6.1 EB-5CG63201SJ 2.8.0(0.309/5/3) 2017-04-01 20:47
x86_64 Cygwin
Machine Type: x86_64-unknown-cygwin

Bash Version: 4.4
Patch Level: 12
Release Status: release



Le lun. 12 nov. 2018 à 16:48, Didou Serge <serge.didou@gmail.com> a écrit :

> Ok, in this case, this should not work either:
>
> mapfile -C xx -c 1 UU  < <( echo -e "Premiere ligne" A{1..45} "\nDeuxieme
> ligne" B{1..45} "\nTroisieme ligne" C{1..45})
>
> But, this form work fine.
>
> Le lun. 12 nov. 2018 à 15:44, Chet Ramey <chet.ramey@case.edu> a écrit :
>
>> On 11/11/18 3:32 PM, Didou Serge wrote:
>>
>> > Bash Version: 4.4
>> > Patch Level: 7
>> > Release Status: release
>> >
>> > Description:
>> > When use mapfile from normal file that call function that use mapfile,
>> the
>> > first mapfile lost data.
>> >
>> > Repeat-By:
>> > I create 3 functions:
>> > ww(){ echo "$@" | mapfile -C yy -c 1 -t TT ; }
>> > xx(){ mapfile -C yy -c 1 -t TT < <(echo "$@") ; }
>> > yy(){ echo "$@" ;}
>> >
>> > I create 1 normal file:
>> > echo -e "Premiere ligne" A{1..45} "\nDeuxieme ligne" B{1..45}
>> "\nTroisieme
>> > ligne" C{1..45} >fic.txt
>> >
>>         [...]
>> > This not work (lost data in second line and after) :
>> > mapfile -C xx -c 1 UU <fic.txt
>> > 0 0 Premiere ligne A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 A12 A13 A14 A15
>> A16
>> > A17 A18 A19 A20 A21 A22 A23 A24 A25 A26 A27 A28 A29 A30 A31 A32 A33 A34
>> A35
>> > A36 A37 A38 A39 A40 A41 A42 A43 A44 A45
>> > 0 1  B17 B18 B19 B20 B21 B22 B23 B24 B25 B26 B27 B28 B29 B30 B31 B32 B33
>> > B34 B35 B36 B37 B38 B39 B40 B41 B42 B43 B44 B45
>> > 0 2 ligne C1 C2 C3 C4 C5 C6 C7 C8 C9 C10 C11 C12 C13 C14 C15 C16 C17 C18
>> > C19 C20 C21 C22 C23 C24 C25 C26 C27 C28 C29 C30 C31 C32 C33 C34 C35 C36
>> C37
>> > C38 C39 C40 C41 C42 C43 C44 C45
>>
>> This is a buffering issue caused by nested calls to mapfile in the same
>> process. The first call to mapfile reads a bufferful of data from the
>> input file, and the second mapfile (the one executed as part of the
>> callback) reads data into that same buffer. When the second call finishes,
>> and the first mapfile is called again, the remaining characters in the
>> buffer have already been discarded. It's not safe to call mapfile as part
>> of a callback to a mapfile invocation.
>>
>> Chet
>> --
>> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>>                  ``Ars longa, vita brevis'' - Hippocrates
>> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>>
>

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: [mapfile]: problem reentrance with normal file Didou Serge <serge.didou@gmail.com> - 2018-11-12 17:00 +0100

csiph-web