Re: Memory protection between compilation units?

On 2025-06-13, Mateusz Viste <mateusz@x.invalid> wrote:

On Fri, 13 Jun 2025 08:00 Bonita Montero wrote:

Therefore I love bounds-checking C++ containers with MSVC (debug
builds) and with the libstdc++ runtime (enabled via macro). (...)
Debug builds are usually much slower, but if you use C++ that's even
more slower since simple things like a container acces via []-operator
occur with a separate function call while debugging. With iterator
-debugging that's even slower. But this price is worth the advantage
that you can easily find bounds-problems with C++.

>
Sounds similar to Pixar's "Electric Fence" that Kaz mentioned earlier:
https://linux.die.net/man/3/efence
>
Depending on the performance impact this may or may not be a viable
solution to debug a rare production issue, but still nice to know it
exists.

Saved my ass back in 1994. I cranked out an event-driven windowing
UI over ncurses and had a crash somewhere. The ncurses guys pointed
me to efence.

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca