Subj : Odd Golded Question? To : andrew clarke From : mark lewis Date : Sun Dec 30 2018 16:21:38 On 2018 Dec 31 06:29:42, you wrote to me: ac> I wrote the first patch for that back in 2014 but it was never ac> accepted upstream. yeah, i know/remember... they were the first to show up in my local searches... i was actually looking for a simple golded compilation script that i thought someone had posted but i wasn't able to find what i thought i remembered... not even after spending a few hours digging back through ozzmosis... ac> Consequently the current version of GoldED still has that bug. yep... funny thing is, once i remembered how to compile golded and got the latest code, i was still seeing the "stack smashing" crash... it wasn't until is suddenly dawned on me that i had rebooted the system and this new wide screen monitor was now better recognized that i got my first clue about the terminal width being the problem... so i went looking for the "[2560]" patch to be sure where to put it... it didn't help and i still had the same problem... so i took that patch back out and built again... then i tried dropping my terminal width and loading golded... that's how i figured out the 255 width limit... heighth didn't seem to matter... the real thing that initially threw me off was the error message changed to the "stack smashing" one... that almost lead me down the wrong rabbit hole at first... ac> I never tested >255 char wide screens with the editor, partly because ac> my fix wasn't accepted upstream, so I forgot about submitting any more ac> patches, but mainly because I never use terminals that large and I ac> didn't expect anyone else to. hehehe... yeah, i spend almost all of my time in one of over a dozen terminal windows i have open at any one time... the majority of them are opened max (fullscreen?)... on this new monitor, that's 271x70 with my current configuration... ac> See the next series of messages for my fixes to the bugs I know about. ac> Be warned I haven't tested them extensively with very large terminals ac> so you're likely to encounter more crashes. i will look... i am happy to say that something certainly has been corrected since my last code update and build... i wasn't able to do any nodelist lookups but now that seems to work... i think i have a little more work to do to get the nodelist stuff working properly (ie: name lookups) but i'll get to that at some point... if anyone has any pointers, they'd be appreciated... right now my nodelist is being compiled into three goldnode.gx[aln] files... )\/(ark Always Mount a Scratch Monkey Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong... .... Give up, you'll only live till you die. --- * Origin: (1:3634/12.73) .