Indeed it is a binary for which a debugger tool like gdb has to be used to analyse it, as detailed at this document on using gdb to analyse Virtuoso core files. Except in your case as you are not using open source and have a prebuilt binary, you would only have to perform steps 6 & 7.
I note you are using a Virtuoso 08.03.3314 binary from May 2019, whereas a an update release 08.03.3316 build was release in Mar 2020. You can download a copy of this updated binary virtuoso-iodbc-t of this binary with debug symbols in tact to enable more details diagnostic on the case of the crash to be obtained.
To use gunzip the file, rename to virtuoso-iodbc-t , replace the existing file of the same name in the bin directory of your installation and restart Virtuoso. The run the problem query again to see if it still crashes and if it does provide a gdb stack trace as detailed in points 6 & 7 of the gdb post.