@ylai@lemmy.ml to C Programming Language@programming.devEnglish • 8 months agoGCC 14 Boasts Nice ASCII Art For Visualizing Buffer Overflowswww.phoronix.comexternal-linkmessage-square5fedilinkarrow-up128arrow-down11cross-posted to: cpp@programming.dev
arrow-up127arrow-down1external-linkGCC 14 Boasts Nice ASCII Art For Visualizing Buffer Overflowswww.phoronix.com@ylai@lemmy.ml to C Programming Language@programming.devEnglish • 8 months agomessage-square5fedilinkcross-posted to: cpp@programming.dev
minus-square@0x0@programming.devlinkfedilink1•8 months agoIt is, our brains are graphical. So is gdbs TUI. Is this another tool? 'Cos ASCII art in compiler output just seems odd to me.
minus-square@RonSijm@programming.devlinkfedilink2•8 months agoNot all features are for everyone. Maybe you’re experienced enough that showing a graph seems like an overkill when you can just read the warnings. But I can imagine for someone that’s more entry level the graphs could make it easier to understand what the problem is
minus-square@sajran@lemmy.mllinkfedilinkEnglish1•8 months agoI mean, it would probably make sense to make this optional to accommodate as many preferences as possible. I, for one, prefer to get the human readable message right away instead of having to use another tool for it.
It is, our brains are graphical. So is
gdbs TUI. Is this another tool? 'Cos ASCII art in compiler output just seems odd to me.Not all features are for everyone. Maybe you’re experienced enough that showing a graph seems like an overkill when you can just read the warnings.
But I can imagine for someone that’s more entry level the graphs could make it easier to understand what the problem is
I mean, it would probably make sense to make this optional to accommodate as many preferences as possible. I, for one, prefer to get the human readable message right away instead of having to use another tool for it.