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

[Alex fxmbsw7 Ratchev]

./bash --noprofile --norc

bash-5.1# ./bash ../xbl5/xbl

malloc: unknown:0: assertion botched
malloc: 0x3000211ab0: allocated: last allocated from glob.c:1150
realloc: underflow detected; mh_nbytes out of range
Aborting...Aborted
bash-5.1#

On Fri, Oct 22, 2021, 17:14 Chet Ramey <chet.ramey@case.edu> wrote:

> On 10/20/21 8:27 PM, Alex fxmbsw7 Ratchev wrote:
> > i see
> > makes sense
> >
> > i was hoping for finished cmds to test / save debugging info , rather
> than
> > for example this git docs
> >
> > i can say it for anyone, ..imho 99 % to all docs are.. not for me
> > like <peep>
> >
> > how to check bash devel version and version history
> > to mark as good / bad
> > .. is one small question about that all
>
> The bottom line is that even with your code, it will take the rest of your
> environment to reproduce the issue. I couldn't reproduce it with what you
> previously posted. I doubt you can reproduce it with `bash --noprofile
> --norc' as well.
>
> The idea behind `git bisect' is to find a commit where it works, find a
> commit where it doesn't (for some value of `it'), and do a binary search on
> commits between those two to find which one starts breaking. `git bisect'
> automates much of this process.
>
> I found this short explainer after about ten seconds of searching:
>
> https://thoughtbot.com/blog/git-bisect
>
> Since the problem appears to be interactive startup, I'm not sure you'll
> be able to automate this, unless something like `bash -i </dev/null'
> reproduces the problem. But `git bisect' can handle most of the process
> for you.
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>