Live data from Hacker News

GCC 14 Boasts Nice ASCII Art for Visualizing Buffer Overflows

phoronix.com

31–40 of 54 posts

Re: GCC 14 Boasts Nice ASCII Art for Visualizing Buffer Overflows

#31
Glad GCC is moving into the direction of human-readable parsing! Back in my day (like 15 years ago) any error would return a stack of unreadable template expansions.

Still, I wonder if GCC is the best tool for this visualisation. Shouldn't it be in the realm of GDB, Valgrind, or other debuggers?

Re: GCC 14 Boasts Nice ASCII Art for Visualizing Buffer Overflows

#34

[flagged]

I wonder why Phoronix enabled such levels of protection? All I can think of is that their forum is pretty toxic. But surely nobody would DDoS phoronix.com just because they were insulted for liking Wayland or, god forbid, Windows.

Re: GCC 14 Boasts Nice ASCII Art for Visualizing Buffer Overflows

#36
post #31

Glad GCC is moving into the direction of human-readable parsing! Back in my day (like 15 years ago) any error would return a stack of unreadable template expansions. Still, I wonder if GCC is the best tool for this visualisation. Shouldn't it be in the realm of GDB, Valgrind, or other debuggers?

Yes, a big warning during compilation is thousand times better than getting it during debugging and profiling. Because everybody must compile, but few people use GDB, and even fewer people use Valgrind.
Post reply on HN