erm im not sure.. it is my rc that bashlinker script i wrote in mails topic 'segfaults on >my< code' in specific on alike arr=( "$path"$glob )
i cannot test much else, i code this only, other bash scripts of others i dunno and till they can code dont wanna know so i can only code on my stuff it used to work new bash compilations broke it as u may have noticed i posted a few weirdnesses and fails already with.. no results to me i can post the tgz of my code here, u can . script it and maybe just maybe it will segf for u too but probably not tho a test its worth else what can i do, tell me status: new bash devel x times new, new sw maybe a bit beta, but official then my pro code, i code pro since 20 years ans it segfaults, where it uses to run, .. not much changes there were ao i got new sw and segf, .. .. can u at least test the tgz ? if that works for you what can i do besides i cant debug it cause i lack.c downgrade ? maybe no good solution the git bad good thing might show something .. On Thu, Oct 21, 2021, 02:27 Chet Ramey <chet.ra...@case.edu> wrote: > On 10/20/21 8:24 PM, Alex fxmbsw7 Ratchev wrote: > > erm sorry what > > The issue, if any, is obviously triggered by something in your environment. > You can run bash --noprofile --norc to verify that. > > No one else has access to everything in your environment. I could not > reproduce the crash with the parts of your startup scripts you posted. > > You are the only one who can reproduce this crash. There is little anyone > can do to help you at this point without you taking the lead to isolate > the crash to either a specific piece of shell code or a specific change > in bash. > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/ >
