It appears that importing orekit_jpype and initializing the VM within a GDB Python session leads to a segfault. Replicating this should be fairly simple as only gdb python, r , import orekit_jpype and orekit_jpype.initVM() are necessary to make the segfault show.
(bskenv) $ gdb python
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...
(gdb) r
Starting program: /home/benjamin/micromamba/envs/bskenv/bin/python
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.10.16 | packaged by conda-forge | (main, Dec 5 2024, 14:16:10) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import orekit_jpype
>>> orekit_jpype.initVM()
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe92005f2 in ?? ()
The segfault message is not specific at all, so any pointers in the right direction are appreciated ! The underlying JVM version I’m using is 23.0.2