The ups and downs of strlcpy()
The ups and downs of strlcpy()
Posted Jul 25, 2012 15:11 UTC (Wed) by paulj (subscriber, #341)In reply to: The ups and downs of strlcpy() by nix
Parent article: The ups and downs of strlcpy()
One reason is debugging stack corruption, where normal tools may not give meaningful backtraces. With frame-pointers, you can easily figure out where earlier, uncorrupted, frames really are, and figuring out why it crashed.
(Log in to post comments)
The ups and downs of strlcpy()
Posted Jul 25, 2012 17:17 UTC (Wed) by nix (subscriber, #2304) [Link]
Yep. That's why frame pointers should be *enableable*. It doesn't mean they should be on by default.


