It's occuring after JCC calls JNI_CreateJavaVM     env = initVM(os.pathsep.join(classpath) or None, **initvm_args)
^^^^^ last python trace before death

Breakpoint 5, initVM (self=0x7ffff7e05048, args=0x7ffff66deac8,
    kwds=0x7ffff7e00ec8) at jcc3/sources/jcc.cpp:527
527             if (JNI_CreateJavaVM(&vm, (void **) &vm_env, &vm_args) < 0)
^^^^ last line of jcc.cpp before death

(gdb) step

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe43942b4 in ?? ()
AFTER fixing debians debugging symbols with ln -s

Breakpoint 1, JNI_CreateJavaVM (vm=0x7fffffffc420, penv=0x7fffffffc418,
    args=0x7fffffffc450) at ./src/hotspot/src/share/vm/prims/jni.cpp:5161
5161    ./src/hotspot/src/share/vm/prims/jni.cpp: No such file or directory.
(gdb) s
JNI_CreateJavaVM (vm=0x7fffffffc420, penv=0x7fffffffc418, args=0x7fffffffc450)
    at ./src/hotspot/src/share/vm/prims/jni.cpp:5163
5163    in ./src/hotspot/src/share/vm/prims/jni.cpp
/build/gdb-A87voC/gdb-7.12/gdb/inline-frame.c:167: internal-error:
void inline_frame_this_id(frame_info*, void**, frame_id*): Assertion
`frame_id_p (*this_id)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it.  For instructions, see:

What in the name of heck

On Wed, Jul 5, 2017 at 11:48 AM, Joshua Campbell <[EMAIL PROTECTED]> wrote:

Joshua Charles Campbell
Ph.D. Student and Research Assistant
Department of Computing Science
University of Alberta