Natanael Copa added the comment:
I created a PR for this https://github.com/python/cpython/pull/24502
--
___
Python tracker
<https://bugs.python.org/issue43
Change by Natanael Copa :
--
keywords: +patch
pull_requests: +23292
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24502
___
Python tracker
<https://bugs.python.org/issu
Natanael Copa added the comment:
This mentions some examples for musl triplets/tuples:
https://wiki.musl-libc.org/getting-started.html
It points to
https://github.com/richfelker/musl-cross-make/blob/master/README.md#supported-targets
which I think is the best documentation. (Rich Felker
Natanael Copa added the comment:
> Do you have glibc and musl installed side by side?
No. But there is nothing preventing me to have the libc runtimes installed in
parallel with glibc.
/lib/libc.so.6
/lib/libc.musl-x86_64.so.1
And it is not common that people copy libc.so.6 (with frie
Natanael Copa added the comment:
The referenced https://wiki.debian.org/Multiarch/Tuples doc says:
> we require unique identifiers for each architecture that identifies an
> incompatible set of libraries that we want to be co-installed.
Since GNU libc and musl libc are not ABI comp
Natanael Copa added the comment:
Does this mean that the SOABI should be the same for python built with musl
libc and GNU libc?
They are not really ABI compatible.
--
___
Python tracker
<https://bugs.python.org/issue43
New submission from Natanael Copa :
The SOABI does not make any difference between GNU libc and musl libc.
Using official docker images:
# debian build with GNU libc
$ docker run --rm python:slim python -c 'import
sysconfig;print(sysconfig.get_config_var("SOABI"))'
cpython-39-x8
Natanael Copa added the comment:
I create a PR for this issue.
It would be nice to have it reviewed.
https://github.com/python/cpython/pull/18380
Thanks!
--
___
Python tracker
<https://bugs.python.org/issue21
Change by Natanael Copa :
--
pull_requests: +17756
pull_request: https://github.com/python/cpython/pull/18380
___
Python tracker
<https://bugs.python.org/issue21
Change by Natanael Copa :
--
nosy: +ncopa
___
Python tracker
<https://bugs.python.org/issue21622>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Natanael Copa :
--
type: -> crash
___
Python tracker
<https://bugs.python.org/issue36107>
___
___
Python-bugs-list mailing list
Unsubscrib
Natanael Copa added the comment:
It seems like python 3.7.2 works. Any idea which commit(s) may have fixed it?
--
___
Python tracker
<https://bugs.python.org/issue36
Natanael Copa added the comment:
Valgrind claims there are some use of uninitialized values.
--
Added file: https://bugs.python.org/file48169/valgrind.out
___
Python tracker
<https://bugs.python.org/issue36
Natanael Copa added the comment:
Interestingly, it does not crash when I run python in valgrind.
--
___
Python tracker
<https://bugs.python.org/issue36
New submission from Natanael Copa :
Alpine Linux's python 3.6.8 native build on aarch64 gets killed by stack
protector when run on Raspberry Pi 3.
It does not happen when same binary runs on packet.net's aarch64 machine.
I was able to get a backtrace by copying the core.
Core was generated
Natanael Copa <natanael.c...@docker.com> added the comment:
Exactly same as previous patch, but refactored to only have a single
pthread_attr_destroy() call instead of 3.
diff --git a/Python/thread_pthread.h b/Python/thread_pthread.h
index b7463c0ca6..1006a168fa 100644
--- a/
Natanael Copa <natanael.c...@docker.com> added the comment:
I suggest a runtime check like this:
diff --git a/Python/thread_pthread.h b/Python/thread_pthread.h
index b7463c0ca6..e9d0f638c9 100644
--- a/Python/thread_pthread.h
+++ b/Python/thread_pthread.h
@@ -34,6 +34,8 @@
Natanael Copa <natanael.c...@docker.com> added the comment:
I ran a test of pthread_attr_getstacksize() on various systems. Here is what
they return:
Linux/glibc: 8388608
MacOS: 524288
FreeBSD 11.1: 0 (ulimit -s gives 524288)
NetBSD 7.1: 4194304
OpenBSD 6.2: 524288
I
Natanael Copa <natanael.c...@docker.com> added the comment:
With "bad assumption" I mean that currently the code assumes that all unknown
systems has big enough default thread stack size. This would not be a "bad
assumption" if POSIX (or any other standard) w
New submission from Natanael Copa <natanael.c...@docker.com>:
Python assumes that the system default thread stack size is big enough for
python, except for OSX and FreeBSD where stack size is explicitly set. With
musl libc the system thread stack size is only 80k, which leads to hard
Changes by Natanael Copa <natanael.c...@docker.com>:
--
title: Various security vulnerabilities in bundled expat -> Various security
vulnerabilities in bundled expat (CVE-2016-0718 and CVE-2016-4472)
___
Python tracker <rep...@bugs.pytho
New submission from Natanael Copa:
cpython bundles expat in Modules/expat/ and needs to be updated to expat-2.2.0
to fix various security vulnerabilities.
21 June 2016, Expat 2.2.0 released.
Release 2.2.0 includes security & other bug fixes.
Security fixes
CVE-2016-0718 (issue 537)
Fix c
22 matches
Mail list logo
