You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (Jira)" <ji...@apache.org> on 2019/08/21 17:36:00 UTC
[jira] [Commented] (ARROW-2652) [C++/Python] Document how to
provide information on segfaults
[ https://issues.apache.org/jira/browse/ARROW-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912545#comment-16912545 ]
Wes McKinney commented on ARROW-2652:
-------------------------------------
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)?
> [C++/Python] Document how to provide information on segfaults
> -------------------------------------------------------------
>
> Key: ARROW-2652
> URL: https://issues.apache.org/jira/browse/ARROW-2652
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Documentation, Python
> Reporter: Uwe L. Korn
> Priority: Major
> Labels: beginner
> Fix For: 0.15.0
>
>
> 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 https://github.com/apache/arrow/issues/2089#issuecomment-393477116
--
This message was sent by Atlassian Jira
(v8.3.2#803003)