C++ Logo


Advanced search

Re: [std-proposals] set_new_handler extension

From: Phil Bouchard <boost_at_[hidden]>
Date: Sat, 18 Feb 2023 23:39:37 -0500
On 2/17/23 12:07, Jason McKesson via Std-Proposals wrote:
> You realize that this proves precisely nothing, right? The source of
> the bug could still be in your code. Switching memory allocators means
> switching where the heap tracking stuff is (and a GPU allocator
> probably puts heap tracking in your CPU's memory rather than GPU
> memory of which there is far less). So a wild-write which on one
> allocator hits heap tracking data, would very likely miss heap
> tracking data on a different allocator. It would hit something else,
> something that your program is able to tolerate better.

Alright I forgot my laptop is dual-boot with Windows 8.1. So I compiled
the application attached using clang++ version 8.0 under Windows and
clang++ version 10.0 under Linux on the *same* laptop of 16 GB of memory.

On Windows, it crashes before printing anything.

On Linux, it works perfectly fine and outputs:

int main(): allocating maximum: 65536 kilobytes.
void test(int): 1
void test(int): 2
void test(int): 4
void test(int): 8
void test(int): 16
void test(int): 32
void test(int): 64
void test(int): 128
int main(): done.

So case closed, I proved my point. The only hope left is to amend the
C++ standards.

Thank you,

Logo <https://www.fornux.com/>  
*Phil Bouchard*  facebook icon
T: (819) 328-4743
E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada
Banner <https://goglobalawards.org/> Le message ci-dessus, ainsi que les
documents l'accompagnant, sont destinés uniquement aux personnes
identifiées et peuvent contenir des informations privilégiées,
confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce
message par erreur, veuillez le détruire.
This communication (and/or the attachments) is intended for named
recipients only and may contain privileged or confidential information
which is not to be disclosed. If you received this communication by
mistake please destroy all copies.

Received on 2023-02-19 04:39:39