bash -xv mystuff
<cut>
+ supported='/@(eval[12]|bin|set|shopt|declare|function|alias|pc|runtime)/*'
<cut>
+ for arg in "$medir" "$@"
+ [[ ! -e /root/xbl5 ]]
++ realpath /root/xbl5
+ rarg=/root/xbl5
+ pos=("$rarg"$supported)
malloc: unknown:0: assertion botched
malloc: 0x3000211a30: allocated: last allocated from glob.c:1150
realloc: underflow detected; mh_nbytes out of range
Aborting...Aborted
bash-5.1#
On Sat, Oct 23, 2021, 03:22 Alex fxmbsw7 Ratchev <fxmb...@gmail.com> wrote:
> its my code, as in the topic of this mail, that makes recent git devels
> segfault, it might as well be unstable version gcc etc fault
>
> i have one two lines same in .profile and .bashrc
> that is source xbl loader with ps1x dir to make it load my ps1... on the
> glob part there i quoted, also glob.c in act shows so too
>
> so bash without it loads
> with xbl segf at arr=( "$path"$glob )
>
> still insist in any terminal session ?
> maybe i should post xbl and co ? its in the other mail for the cascade dude
>
> On Sat, Oct 23, 2021, 03:10 Greg Wooledge <g...@wooledge.org> wrote:
>
>> On Sat, Oct 23, 2021 at 03:03:31AM +0200, Alex fxmbsw7 Ratchev wrote:
>> > ./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
>>
>> Originally you said you got a segfault when you ran "./bash".
>> This invokes an interactive shell.
>>
>> But now, instead of showing us a crash when you run "./bash" (or
>> "./bash --noprofile --norc"), you're running a script.
>>
>> It's very hard to figure out what you're doing if you keep switching
>> things around.
>>
>> You've also got "./bash --noprofile --norc" floating in the body of your
>> email with no context. We can't tell what this means. Did you run it?
>> If so, why isn't there a visible shell prompt in front of it?
>>
>> Did you simply quote it from Chet's email?
>>
>> Please make it easier to help you by being clear. Show us the actual
>> terminal session which demonstrates the problem. This means showing
>> us *whole* lines, starting from column 1, with your shell prompts and
>> everything.
>>
>>
