Skip to content
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

[C++/Python] Document how to provide information on segfaults #19047

Open
asfimport opened this issue May 31, 2018 · 1 comment
Open

[C++/Python] Document how to provide information on segfaults #19047

asfimport opened this issue May 31, 2018 · 1 comment

Comments

@asfimport
Copy link
Collaborator

asfimport commented May 31, 2018

We often have users that report segmentation faults in pyarrow. This will sadly keep reappearing as we also don't have the magical ability of writing 100%-bug-free code. Thus we should have a small section in our documentation on how people can give us the relevant information in the case of a segmentation fault. Preferably the documentation covers gdb and lldb. They both have similar commands but differ in some minor flags.

For one of the example comments I gave to a user in tickets see #2089 (comment)

Reporter: Uwe Korn / @xhochy

Related issues:

Note: This issue was originally created as ARROW-2652. Please see the migration documentation for further details.

@asfimport
Copy link
Collaborator Author

Wes McKinney / @wesm:
Seems like a smallish patch in developer/python.rst should do the trick. Does someone have experience with lldb (I only am familiar with gdb)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant