this crash didnt appear, i think, but my code constillation may have
chamged, with some weeks or month old dev build
On Wed, Oct 13, 2021, 03:15 Alex fxmbsw7 Ratchev wrote:
> could you give me maybe good urls about such to learn ( maybe not too long
> ones .. ) ?
>
> i can paste the two missing
could you give me maybe good urls about such to learn ( maybe not too long
ones .. ) ?
i can paste the two missing functions
or even paste the archive where they come from ( this same project )
it may also be non bash errors cause more newer sw used than usual.. no
idea..
to paste minimally
On 2021-10-12 at 00:48 +0700, Robert Elz wrote:
> | When execve returns this error for what is a clearly invalid
> reason,
>
> The problem is that sometimes it will probably be an invalid reason
> (that's where the race conditions can matter, that the file was there
> when it was checked
Le mar. 05 oct. 2021 16h12 -0400, Chet Ramey a écrit :
> On 10/5/21 1:50 PM, Dominique Martinet wrote:
> > If I change malloc_usable_size to return p->mh_nbytes instead of
> > maxbytes, then the crash disappears.[2]
>
> That's the right fix.
Chet, when you'll have time, would you mind publishing
On 10/11/21 11:17 AM, Alex fxmbsw7 Ratchev wrote:
> as the topic says
> i fetched it earlier today, compiled, and tho it rather segfaults
>
> due to i dunno to debug this, this mail consists of 3 parts, 1 gdb + bt
> ./bash (loading in bashrc a script which makesnit segfault)
> and once with gdb
i updated sys [lil] and fetched bash dev git again, still segfaults
gdb output looks different
btw it looks wonderful informative, must be new gcc gdb or so.. for the
first time i see such explaintive every function name with details
the dl err is proot ( chroot alike ) i guess
i see there the
