hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3757) libhdfs: improve native stack traces
Date Fri, 03 Aug 2012 02:42:02 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427814#comment-13427814
] 

Colin Patrick McCabe commented on HDFS-3757:
--------------------------------------------

Here's an example of a stack trace _without_ the patch:
{code}
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGFPE (0x8) at pc=0x00007faf6092a078, pid=29084, tid=140389502605056
#
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libhdfs.so.0.0.0+0x4078]  unsigned char+0x58
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
{code}

Here's an example of a stack trace _with_ the patch:
{code}
*** Got signal 8 (Floating point exception)! ***
/home/cmccabe/hadoop1/hadoop-hdfs-project/hadoop-hdfs/target/native/target/usr/local/lib/libhdfs.so.0.0.0(+0x8054)[0x7fd29fcc3054]
/usr/local/lib/libjvm.so(+0x71150a)[0x7fd29f5a450a]
/usr/local/lib/libjvm.so(+0x70e4ab)[0x7fd29f5a14ab]
/usr/local/lib/libjvm.so(JVM_handle_linux_signal+0x170)[0x7fd29f5a4ff0]
/usr/local/lib/libjvm.so(+0x70e3be)[0x7fd29f5a13be]
/lib64/libpthread.so.0(+0xfd00)[0x7fd29faadd00]
/home/cmccabe/hadoop1/hadoop-hdfs-project/hadoop-hdfs/target/native/target/usr/local/lib/libhdfs.so.0.0.0(hdfsOpenFile+0x6b)[0x7fd29fcbf33b]
./hadoop-hdfs-project/hadoop-hdfs/target/native/test_libhdfs_threaded[0x401737]
./hadoop-hdfs-project/hadoop-hdfs/target/native/test_libhdfs_threaded[0x401f00]
/lib64/libpthread.so.0(+0x7f05)[0x7fd29faa5f05]
/lib64/libc.so.6(clone+0x6d)[0x7fd29ebde10d]
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGFPE (0x8) at pc=0x00007fd29fcbf33b, pid=1087, tid=140540761745152
#
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libhdfs.so.0.0.0+0x433b]  unsigned char+0x6b
#
# An error report file with more information is saved as:
# /home/cmccabe/hadoop1/hs_err_pid1087.log
2012-08-02 19:39:19,416 INFO  FSNamesystem.audit (FSNamesystem.java:logAuditEvent(252)) -
allowed=true  ugi=cmccabe (auth:SIMPLE)       ip=/127.0.0.1   cmd=mkdirs      src=/tlhData0001
       dst=null        perm=cmccabe:supergroup:rwxr-xr-x
Segmentation fault
{code}

There's a lot more information in the latter. including the name of the function where the
problem occurred.
                
> libhdfs: improve native stack traces
> ------------------------------------
>
>                 Key: HDFS-3757
>                 URL: https://issues.apache.org/jira/browse/HDFS-3757
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: libhdfs
>    Affects Versions: 2.2.0-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>         Attachments: HDFS-3757.001.patch
>
>
> When libhdfs crashes, we often don't get very good stack traces.  It would be nice to
get a better stack trace for the thread that crashed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message