-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[BUG]: Python3.11 error_already_set.what()
segfault
#4853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I know it's not much of a reproduction, but if you could have a look at the stacktrace and theorycraft why this segfault occurs that would be extremely helpful already. I can't figure out why |
I think this is related to #4863 |
Unsure if related / this is the same issue, but I can also reproduce it on indentation errors (python 3.11, pybind 2.12.0), here's the stacktrace:
And some info about the error:
|
Required prerequisites
What version (or hash if on master) of pybind11 are you using?
2.11.1
Problem description
I run an import of pyarrow and attempt to create a Table from a Pandas DataFrame
this throws an exception, which I catch:
py::error_already_set.what()
causes the segfault.Reproducible example code
I maintain an opensource repo and I absolutely hate it when I get an issue without a reproduction example, but in this case I can't really make one as it's wrapped into an application and only occurs when run together with multiple tests.
(Just running the test where the segfault occurs does not reproduce the issue)
I have however attached lldb and have a stacktrace that hopefully provides more information:
Python version:
Python 3.11.0rc1
(Docker) Linux version:
Linux f63acc518afb 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
On Python3.9 the issue is not reproducable
The text was updated successfully, but these errors were encountered: