Hi, It seems to be a stale object issue in my case. I did a "make clean" and a "make all" and the core problem went away. DISPLAY works normally for me now.
Dave -----Original Message----- From: Dave Birdsall [mailto:[email protected]] Sent: Tuesday, September 26, 2017 1:57 PM To: [email protected] Subject: Core when trying to use DISPLAY in Trafodion? Hi, I'm doing some Optimizer debugging on the latest version of Trafodion. Today I tried using the DISPLAY gui tool because I wanted to see how a join query was being optimized. However, it seems to core no matter what query I try: (gdb) bt 3 #0 0x00007ffff5117625 in raise () from /lib64/libc.so.6 #1 0x00007ffff5118e05 in abort () from /lib64/libc.so.6 #2 0x00007ffff6ef2165 in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so (More stack frames follow...) (gdb) bt #0 0x00007ffff5117625 in raise () from /lib64/libc.so.6 #1 0x00007ffff5118e05 in abort () from /lib64/libc.so.6 #2 0x00007ffff6ef2165 in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #3 0x00007ffff706685f in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #4 0x00007ffff7066f2b in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #5 0x00007ffff6ef0e44 in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #6 0x00007ffff6ef6c65 in JVM_handle_linux_signal () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #7 <signal handler called> #8 0x00007ffff6ee87bf in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #9 0x00007ffff7065891 in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #10 0x00007ffff70663cd in ?? () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #11 0x00007ffff6ef6d02 in JVM_handle_linux_signal () from /usr/lib/jvm/java-1.7.0-openjdk.x86_64/jre/lib/amd64/server/libjvm.so #12 <signal handler called> #13 0x00007fffd2eb2d9d in SqldbgSetPointers (memoptr=0x0, tasklist=0x0, ---Type <return> to continue, or q <return> to quit---q analysisQuit (gdb) frame 13 #13 0x00007fffd2eb2d9d in SqldbgSetPointers (memoptr=0x0, tasklist=0x0, analysis=0x7fffd32a9bf8, currentContext=0x7fffe263c090, ClusterInfo=<value optimized out>) at ExportFunctionSqlCmpDbg.cpp:84 84 CURRSTMT_OPTGLOBALS->memo = (CascadesMemo *) memoptr; It seems the address CURRSTMT_OPTGLOBALS->memo is zero; we are trying to dereference a zero pointer. It's been a month or so since I've played with this tool. I'm wondering if others are encountering this core also? Thanks, Dave
