harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3117) [db2] IBM DB2 JDBC "sample apps" crash on exit
Date Mon, 14 Jan 2008 20:48:35 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558773#action_12558773
] 

Gregory Shimansky commented on HARMONY-3117:
--------------------------------------------

I reproduced the crash on Fedora Core x86_64 on Harmony M4. From what I can tell, the bug
is again with some library unloading, although it doesn't seem to be related to stack unwinding
as I thought. Running the sample under gdb gives the following:

Program received signal SIGSEGV, Segmentation fault.
0x00002aaac0a838fa in ?? ()
(gdb) bt
#0  0x00002aaac0a838fa in ?? ()
#1  0x00002aaac08ff1c8 in ?? ()
#2  0x00000037a5219be0 in _dl_argv_internal () from /lib64/ld-linux-x86-64.so.2
#3  0x0000000000000000 in ?? ()
(gdb) x/1i $rip
0x2aaac0a838fa: Cannot access memory at address 0x2aaac0a838fa

The value of RIP seems to be ok but gdb cannot show memory addressed by it. I suppose some
library was there a moment before crash. I'm trying to build Harmony now to check memory map
just before shutdown in JNI_DestroyJavaVM. This way I'll know which library resided on the
crash address.

> [db2] IBM DB2 JDBC "sample apps" crash on exit
> ----------------------------------------------
>
>                 Key: HARMONY-3117
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3117
>             Project: Harmony
>          Issue Type: Bug
>          Components: App-Oriented Bug Reports
>         Environment: EM64T -- RedHat Enterprise Linux 4 - U4
> IBM DB2 Express-C version9.1 
> Latest Harmony JRE binary download (vn = r487452, (Dec 15 2006), Linux/em64t/gcc 4.0.3,
release build)
>            Reporter: Chris Elford
>            Assignee: Gregory Shimansky
>            Priority: Critical
>             Fix For: 5.0M4
>
>         Attachments: db2-setup.zip
>
>
> Putting critical because critical is defined as "Crashes, loss of data, severe memory
leak."
> I was experimenting with whether DB2 JDBC connection will work with Harmony.    I am
using the sample apps that come with DB2.  The JDBC layer appears to connect to the database
successfully (which is good for Harmony) and queries appear to work (data comes thru).   However,
during shutdown of the sample apps, the process regularly segfaults when using Harmony and
exits cleanly using the BEA JRE and Sun JRE.
> crash behavior is consistent with both "java DbConn" (basic connection test) and "java
TbSel" (basic sql select test) sample apps that come with the "free" version of DB2.
> unfortunately, the core file provides little insight.  
> (gdb) bt
> #0  0x0000002aaf5898fa in ?? ()
> #1  0x0000000000000000 in ?? ()
> (gdb) info threads
> * 1 process 22262  0x0000002aaf5898fa in ?? ()
> Attaching with debugger gives a possible hint:
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000002aaf5898fa in OSSHLibrary::unload ()
>    from /home/db2inst/sqllib/lib64/libdb2osse.so.1
> (gdb) bt
> #0  0x0000002aaf5898fa in OSSHLibrary::unload ()
>    from /home/db2inst/sqllib/lib64/libdb2osse.so.1
> #1  0x0000002aacce93de in sqlexPluginUnload ()
>    from /home/db2inst/sqllib/lib64/libdb2.so.1
> #2  0x0000002aad1dd080 in sqlexAppLibTerm ()
>    from /home/db2inst/sqllib/lib64/libdb2.so.1
> #3  0x0000002aacc41afa in sqlmStreamFlagsAction ()
>    from /home/db2inst/sqllib/lib64/libdb2.so.1
> #4  0x0000002aacc41b83 in _ZN10appLibInitD9Ev ()
>    from /home/db2inst/sqllib/lib64/libdb2.so.1
> #5  0x0000002aacc41b73 in appLibInit::~appLibInit ()
>    from /home/db2inst/sqllib/lib64/libdb2.so.1
> #6  0x000000380df30c45 in exit () from /lib64/tls/libc.so.6
> #7  0x000000380df1c402 in __libc_start_main () from /lib64/tls/libc.so.6
> #8  0x000000000040096a in _start () at ../sysdeps/x86_64/elf/start.S:113
> It looks to me that the C++ destructors registered by some presumably JNI components
are being invoked by the C runtime at process exit.  At this time there are no other threads
remaining (i.e., java looks like it is done and gone) and presumably during the cleanup process
something gets out of control.
> In contrast with the Sun Java5 JRE, there are 13 other threads remaining when the destructor
runs and 12 other threads with the BEA Java5 JRE.
> I'm  not sure if this is a compatibility issue with the reference implementation or if
is simply a hole in the JNI support that Harmony currently provides.  It appears to be 100%
reproducable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message