[issue44411] regrtests fail with segfault after failing calls to malloc

[Jack DeVries]

Jack DeVries  added the comment:

I'm closing this because I have the sense that this is a problem with my 
system, but I'm continuing to investigate.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44411] regrtests fail with segfault after failing calls to malloc

[Jack DeVries]

Change by Jack DeVries :


--
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44411] regrtests fail with segfault after failing calls to malloc

[Jack DeVries]

Change by Jack DeVries :


--
keywords: +patch
pull_requests: +25295
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/26707

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44411] regrtests fail with segfault after failing calls to malloc

[Jack DeVries]

Change by Jack DeVries :


--
components: +Library (Lib), macOS
nosy: +ned.deily, ronaldoussoren

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44411] regrtests fail with segfault after failing calls to malloc

[Jack DeVries]

New submission from Jack DeVries :

When running regrtests via `./python.exe -m test` on my system, several 
warnings about failing calls to malloc are generated during `test_decorators`. 
Then, a segmentation fault happens shortly thereafter in `test_descrtut`.

The most recent commit on the main branch as of this test run was 
17b16e13bb444001534ed6fccb459084596c8bcf.

Here are some details about my system:

Model Name: MacBook Pro
  Model Identifier: MacBookPro12,1
  Processor Name:   Dual-Core Intel Core i5
  Processor Speed:  2.7 GHz
  Number of Processors: 1
  Total Number of Cores:2
  L2 Cache (per Core):  256 KB
  L3 Cache: 3 MB
  Hyper-Threading Technology:   Enabled
  Memory:   8 GB
  System Firmware Version:  427.0.0.0.0
  SMC Version (system): 2.28f7
  Serial Number (system):   C02P9EMTFVH5
  Hardware UUID:ABA9DB61-5A93-54BC-8057-6F0E0DA6544B
  Provisioning UDID:ABA9DB61-5A93-54BC-8057-6F0E0DA6544B



Here is the full output from cloning all the way down to segfault
=


➜  tmp.kw3WJpEs git clone g...@github.com:python/cpython.git . --depth=1
Cloning into '.'...
remote: Enumerating objects: 4779, done.
remote: Counting objects: 100% (4779/4779), done.
remote: Compressing objects: 100% (4362/4362), done.
remote: Total 4779 (delta 488), reused 1570 (delta 314), pack-reused 0
Receiving objects: 100% (4779/4779), 24.71 MiB | 11.00 MiB/s, done.
Resolving deltas: 100% (488/488), done.
Updating files: 100% (4537/4537), done.
➜  tmp.kw3WJpEs git:(main) ./configure --with-pydebug
checking for git... found
checking build system type... x86_64-apple-darwin20.5.0
checking host system type... x86_64-apple-darwin20.5.0
checking for python3.11... no
checking for python3... python3
checking for --enable-universalsdk... no
checking for --with-universal-archs... no
checking MACHDEP... "darwin"
Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
--with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for a sed that does not truncate output... /usr/bin/sed
checking for --with-cxx-main=... no
checking for g++... no
configure:

  By default, distutils will build C++ extension modules with "g++".
  If this is not intended, then set CXX on the configure command line.
  
checking for the platform triplet based on compiler characteristics... darwin
checking for -Wl,--no-as-needed... no
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for the Android API level... not Android
checking for --with-suffix... 
checking for case-insensitive build directory... yes
checking LIBRARY... libpython$(VERSION)$(ABIFLAGS).a
checking LINKCC... $(PURIFY) $(MAINCC)
checking EXPORTSYMS... 
checking for GNU ld... no
checking for --enable-shared... no
checking for --enable-profiling... no
checking LDLIBRARY... libpython$(VERSION)$(ABIFLAGS).a
checking for ar... ar
checking for readelf... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for --with-pydebug... yes
checking for --with-trace-refs... no
checking for --with-assertions... implied by --with-pydebug
checking for --enable-optimizations... no
checking PROFILE_TASK... -m test --pgo --timeout=$(TESTTIMEOUT)
checking for --with-lto... no
checking for llvm-profdata... no
configure: llvm-profdata found via xcrun: /usr/bin/xcrun llvm-profdata
checking for -Wextra... yes
checking whether gcc accepts and needs -fno-strict-aliasing... no
checking if we can turn off gcc unused result warning... yes
checking if we can turn off gcc unused parameter warning... yes
checking if we can turn off gcc missing field initializers warning... yes
checking if we can turn on gcc mixed sign comparison warning... yes
checking if we can turn on gcc unreachable code warning... no
checking if we can turn on gcc strict-prototypes warning... yes
checking if we can make implicit