The Logo issue is likely related to lack of support of HII Sections in PE/COFF for the XCODE toolchain. It is the same reason these commands[1] are not included in the OVMF build. I submitted some patches a while back to fix this, I need to follow as I’m not sure they got integrated. So the logo issue is not related.
Is the system hung or just not working? If it is hung you can try and attach via lldb to see your location. If it is just not working then I think you will need to do the DEBUG prints that Laszlo mentioned.
In general if you have XCODE specific issues it is often time related to clang being so aggressive about optimizing out undefined behavior.
If you pass ` -gdb tcp::9000` to QEMU you can attach with lldb via:
lldb -o "settings set plugin.process.gdb-remote.target-definition-file x86_64_target_definition.py" -o "gdb-remote 9000"
You only need the plugin.process.gdb-remote.target-definition-file if you have an older lldb and older QEMU. Long story but lldb did not support the XML description of the target. If this works you will get registers and an unsymbolicated backtrace.
|
!if $(TOOL_CHAIN_TAG) != "XCODE5"
|
| ShellPkg/DynamicCommand/TftpDynamicCommand/TftpDynamicCommand.inf {
|
| <PcdsFixedAtBuild>
|
| gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
|
| }
|
| ShellPkg/DynamicCommand/HttpDynamicCommand/HttpDynamicCommand.inf {
|
| <PcdsFixedAtBuild>
|
| gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
|
| }
|
| OvmfPkg/LinuxInitrdDynamicShellCommand/LinuxInitrdDynamicShellCommand.inf {
|
| <PcdsFixedAtBuild>
|
| gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
|
| }
|
| !endif
|
|
Thanks,
Andrew Fish
Hi Andrew, Liming,
can you please take a look at
<
https://bugzilla.tianocore.org/show_bug.cgi?id=3006>? Daniele has a
quite specific VM setup with OVMF, and it only causes an issue if the
OVMF binary was built on OSX with XCODE5. I'm out of ideas.
Thanks,
Laszlo