sgx-gdb does not work with sgx_create_enclave_from_buffer_ex

[sethmoo]

If an enclave is loaded with sgx_create_enclave_from_buffer_ex, then the sgx-gdb doesn't work. We get a Python exception every time the gdb extension script is called:
Python Exception <class 'gdb.error'> No symbol table is loaded. Use the "file" command.:

It appears that retrieve_enclave_info assumes the enclave was loaded by file:

linux-sgx/sdk/debugger_interface/linux/gdb-sgx-plugin/gdb_sgx_plugin.py

Line 355 in 5db5a81

enclave_path = struct.unpack_from(fmt, name_str)[0].decode(encoding='UTF-8')

If an enclave is loaded from a buffer the debug_enclave_info_t object won't have lpFileName populated. Thus, the debugger extensions cannot load the symbols, and gdb gets quite sad.

[andyzyb]

I think this is expected. The current design of sgx-gdb needs the enclave file to support debugging.

[sethmoo]

If the enclave is loaded via buffer, couldn't the gdb plugin gather the symbol information from the buffer itself? IIRC, the buffer is no different from an external file, in terms of contents. It's just loaded from memory instead of an external file. Thus, all the information needed to load symbols should still be there.