[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: I would probably put all that code in a separate function like init_darwin_libc(), and call init_darwin_libc() in pymain_init(). The real fun will start when we figure out which OS X versions support this feature. I hope we have a buildbot for each. :-)

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: Ok, I will try to do this in the coming days. Is adding this kind of super ugly, super specific code to pymain_init() ok? -- ___ Python tracker

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: > What about overriding the default to DEBUG_WRITE_ON_CRASH if > MallocDebugReport is not set? That sounds like a very good compromise! -- ___ Python tracker

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: > I have two observations: > > First, I think that the default DEBUG_WRITE_ALWAYS, which is the cause > of this issue, is not C standard conforming -- The standard does not > permit implementation defined diagnostics (global side effects!) on a > completely

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: I have two observations: First, I think that the default DEBUG_WRITE_ALWAYS, which is the cause of this issue, is not C standard conforming -- The standard does not permit implementation defined diagnostics (global side effects!) on a completely normal

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: Would it be possible to wrap malloc_print_configure() (https://github.com/PureDarwin/libmalloc/blob/e37056265821cd6e014ab911d9fe3b9d0da88e22/src/malloc_printf.c#L59) in a context manager that we put in test.support? or to override

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: Thanks for checking, it's a pity that os.putenv() does not work. There's a global variable malloc_logger that is set from the environment on startup: https://opensource.apple.com/source/libmalloc/libmalloc-53.1.1/src/malloc.c It seems to be always checked for

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: I forgot to say that MallocLogFile=/dev/null did not work, that's why I tried MallocDebugReport. -- ___ Python tracker ___

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: Thanks, I found "MallocDebugReport" in `man malloc` (I could have thought to look into there...) that seem to do the trick: $ MallocDebugReport=none ./python -m test test_decimal -m test_maxcontext_exact_arith 0:00:00 load avg: 1.27 Run tests sequentially

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Change by Ned Deily : -- nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: "squashing the remark" means suppressing the message from malloc(). I would really like it if the test could be executed by default though. Looking at:

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: > The annoying "error" looks the same as #5614, which was closed as "won't fix". Yes, it's a similar message, test_io does not display it on Catalina anymore thought. > Is this the only place in the test suite now? As far as I know yes. > If it is, I'm

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: The annoying "error" looks the same as #5614, which was closed as "won't fix". Is this the only place in the test suite now? If it is, I'm okay with squashing the remark. -- nosy: +skrah versions: +Python 3.9 ___

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

New submission from Rémi Lapeyre : Here's the result of "./python -m test test_decimal -m test_maxcontext_exact_arith": 0:00:00 load avg: 1.33 Run tests sequentially 0:00:00 load avg: 1.33 [1/1] test_decimal python(7835,0x11a218dc0) malloc: can't allocate region :***