[
https://issues.apache.org/jira/browse/HDFS-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160945#comment-14160945
]
Colin Patrick McCabe commented on HDFS-7010:
--------------------------------------------
bq. I wonder, why the code needs to unwind the stack?
It is used to put stack traces in exceptions.
I agree that this might not really be needed and possibly we could get rid of
it. In my experience, getting stack unwinding code to work properly on
multiple architectures and platforms is difficult, and the benefit seems
uncertain since we could always add more identifying information to each
exception to know where it came from. [~wangzw], what do you think?
> boot up libhdfs3 project
> ------------------------
>
> Key: HDFS-7010
> URL: https://issues.apache.org/jira/browse/HDFS-7010
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Zhanwei Wang
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-7010-pnative.003.patch,
> HDFS-7010-pnative.004.patch, HDFS-7010-pnative.004.patch, HDFS-7010.patch
>
>
> boot up libhdfs3 project with CMake, Readme and license file.
> Integrate google mock and google test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
