[
https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980812#comment-13980812
]
huang ken commented on HDFS-6254:
---------------------------------
Chris Nauroth, thanks a lot for your explanation about gdb SIGSEGV handling &
programming advice.
But <b>hdfsConnect</b> or <b>hdfsBuilderConnect</b> do return <b>not NULL</b>
while namenode not connected in my test, not the same as the declaration in
hdfs.h. Is it right ?
> hdfsConnect segment fault where namenode not connected
> ------------------------------------------------------
>
> Key: HDFS-6254
> URL: https://issues.apache.org/jira/browse/HDFS-6254
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: libhdfs
> Affects Versions: 2.2.0
> Environment: Linux Centos 64bit
> Reporter: huang ken
> Assignee: Chris Nauroth
>
> When namenode is not started, the libhdfs client will cause segment fault
> while connecting.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
