Re: the alias bugger maybe again
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 release. > > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/ >
Re: the alias bugger maybe again
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'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: Misleading error when attempting to run foreign executable
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 case. > > > > [EINVAL] The new process image file has appropriate privileges and > > has a recognized executable binary format, but the system does not > > support execution of a file with this format. > > > I think the most fitting is EINVAL, as Robert said. Did someone tell > the Linux kernel people, so they can fix this? Otherwise I will. > > > > Andrea Monaco > >
Re: Misleading error when attempting to run foreign executable
> [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, but the system does not > support execution of a file with this format. I think the most fitting is EINVAL, as Robert said. Did someone tell the Linux kernel people, so they can fix this? Otherwise I will. Andrea Monaco
Re: current bash.git.devel segfaults on my code
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 able to run > > make clean > make valgrind > > That disables some bash malloc wrapping functions that confuse valgrind > severely. Then just run > > valgrind bash > or > valgrind --leak-check=full bash > > and see what you get. (Assuming you have valgrind installed, of course, and > depending on what you want to find out). > > If you want to try address sanitizer, make sure you have a compiler that > supports it, then run > > make clean > make asan > > I put the shorthand targets in for convenience. Once you build a bash with > address sanitizer support, you just have to run it and see what it reports. > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/ >
Re: current bash.git.devel segfaults on my code
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 severely. Then just run valgrind bash or valgrind --leak-check=full bash and see what you get. (Assuming you have valgrind installed, of course, and depending on what you want to find out). If you want to try address sanitizer, make sure you have a compiler that supports it, then run make clean make asan I put the shorthand targets in for convenience. Once you build a bash with address sanitizer support, you just have to run it and see what it reports. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
