Run with: bash -c 'read -e' < file # patched bash
File base64:
KgMSGQX//wD/NBs1NTUbNRITNTU13TVGFgkVNTU1NdA1RhYJBTUzNdA1Rp4HB2BJYAcH9QcGAAAL
C2AzNdA1Rj0HB2BJBwYAAAsLAQBgYAIAgAiZgBVZYCAbAAEArq6urq6urq6urq6u/4Cu
rq6urq6urq6urq4AAWAZGRkZ5AAQGv9AoBsF
The error under ASAN:
==31690==ERROR: Add
Ran: bash -c 'read -e' < file # patched read to read from file
file Base64:
L/sFfwh+NRgqGHUcb39AfxsDAAACAIABIf+qANqAABsF6+M8KDyAAP7/qgDagAAbBevj
T0wgTYAnAAIAJgkJAAD+/6r///8JCQkAAAIA5vYJCQl6GzgAvBTgJf22G4A3/xuFhYWFhYVw
hYUXhYWFhYWF/xv/QHyAFAH/G/9AZIAyAQYbGVQE3i8UlhTelmQAGiIuVBAAwxQAABA
Why not unalias -a instead of simply going for cp? That way you know for a
fact that nothing has been changed
On Thu, May 18, 2017 at 8:59 PM, Ángel wrote:
> I'm afraid you will have to rewrite the function just to get this
> slightly different result (maybe you can source again that section of
I'm afraid you will have to rewrite the function just to get this
slightly different result (maybe you can source again that section of
the file?) :/
On 5/18/17 2:29 AM, Zoltán Herczeg wrote:
>> I read this as saying that it's a requirement on the application to ensure
>> that character classes are correctly formed, and it's unspecified behavior
>> if they're not.
>>
>> So you're right: people should not count on shells treating improperly-
>> f
On Thu, May 18, 2017 at 08:29:13AM +0200, Zoltán Herczeg wrote:
> I think throwing an error would be better than an undefined behaviour. Bash
> throws error for solo parenthesis, a similar technique could be used here.
That's not really an option, because an unmatched [ isn't a syntax
error. It'
