Re: the alias bugger maybe again

2021-10-13 Thread Alex fxmbsw7 Ratchev
thanks im still bit struggeling at the debugging of devel, brb.. On Wed, Oct 13, 2021, 16:31 Chet Ramey wrote: > On 10/11/21 3:08 PM, Alex fxmbsw7 Ratchev wrote: > > the alias bug(s) i experience again in simple code > > This is fixed in the devel branch, and the fix will be in the next

Re: the alias bugger maybe again

2021-10-13 Thread Chet Ramey
On 10/11/21 3:08 PM, Alex fxmbsw7 Ratchev wrote: the alias bug(s) i experience again in simple code This is fixed in the devel branch, and the fix will be in the next release. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' -

Re: Misleading error when attempting to run foreign executable

2021-10-13 Thread Alex fxmbsw7 Ratchev
also enoexist with its description of the ld parser not available On Wed, Oct 13, 2021, 16:06 Andrea Monaco wrote: > > > [ENOENT] A component of path or file does not name an existing file > > or path or file is an empty string. > > > Then ENOENT is clearly not an appropriate error in this

Re: Misleading error when attempting to run foreign executable

2021-10-13 Thread Andrea Monaco
> [ENOENT] A component of path or file does not name an existing file > or path or file is an empty string. Then ENOENT is clearly not an appropriate error in this case. > [EINVAL] The new process image file has appropriate privileges and > has a recognized executable binary format,

Re: current bash.git.devel segfaults on my code

2021-10-13 Thread Alex fxmbsw7 Ratchev
thank you much sir ill examine your instructions On Wed, Oct 13, 2021, 15:27 Chet Ramey wrote: > On 10/12/21 9:15 PM, Alex fxmbsw7 Ratchev wrote: > > could you give me maybe good urls about such to learn ( maybe not too > long > > ones .. ) ? > > You should, with a current bash devel, just be

Re: current bash.git.devel segfaults on my code

2021-10-13 Thread Chet Ramey
On 10/12/21 9:15 PM, Alex fxmbsw7 Ratchev wrote: could you give me maybe good urls about such to learn ( maybe not too long ones .. ) ? You should, with a current bash devel, just be able to run make clean make valgrind That disables some bash malloc wrapping functions that confuse valgrind