Can you whittle this down to the smallest reproducer and post a stand-alone
synthetic testcase with sample input data that fails?
If the goal is simulating "exported arrays", there are other methods that
would probably work out better.
--
Dan Douglas
Greg Wooledge wrote:
> On Wed, Mar 27, 2013 at 02:37:16PM -0700, Linda Walsh wrote:
>> Greg Wooledge wrote:
> Array variables may not (yet) be exported.
>>> Associative arrays can't be exported either.
>
>> Yeah, but they seem to get propagated anyway, I must save it somewhere
>>
On Wed, Mar 27, 2013 at 02:37:16PM -0700, Linda Walsh wrote:
> Greg Wooledge wrote:
> >>> Array variables may not (yet) be exported.
> > Associative arrays can't be exported either.
> Yeah, but they seem to get propagated anyway, I must save it somewhere
> like
> I do _FPATH... i.e. e
On 03/26/2013 03:23 PM, Chet Ramey wrote:
> On 3/25/13 6:45 PM, Pádraig Brady wrote:
>
>> OK thanks for the pointer.
>> So the race is narrowed rather than closed?
>> As we have:
>>
>> execute_disk_command()
>> {
>> int pid = fork();
>> if (pid == 0) /* child */
>> {
>>CHECK_SIGTER
