Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Mateusz Viste <mateusz@x.invalid>
Newsgroups: comp.lang.c
Subject: Re: Memory protection between compilation units?
Date: Fri, 13 Jun 2025 08:47:17 +0200
Organization: ...
Lines: 18
Message-ID: <20250613084717.2889aa4b@mateusz>
References: <20250611153239.6bc43323@mateusz>
	<102geq8$38k6o$1@raubtier-asyl.eternal-september.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 13 Jun 2025 08:47:18 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="be0ae288ae1b46b70a4e7a2b5ac6f308";
	logging-data="3444324"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+5arE8O2lQ2SV1tgOajvGz"
Cancel-Lock: sha1:TLwow1pS/oarB55Z4MW8rLgtldY=
X-Newsreader: Claws Mail 4.2.0 (GTK 3.24.43; x86_64-suse-linux-gnu)

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.

Mateusz