On 04/20/18 10:38, Johannes Swoboda wrote: > Hello again, > > Thank you again for taking the time to help me with this. > > On 2018-04-20 17:58, Palmer, Thomas wrote: >> Also, did you start qemu with the "-s" option before you started gdb? > > Unfortunately, I start qemu with -s -S; then, I attach gdb. I know the > attaching works because I gdb accepts the continue command which > instructs qemu to begin execution of the virtual machine. > The source [...]/gdb_uefi.py command seems to work find, but reload-efi > -o [...]/DEBUG/GdbSyms.dll throws the error "No type named > EFI_SYSTEM_TABLE_POINTER". ... > Do you have any other suggestions?
I'm not sure things have loaded to the point necessary by then. I'd suggest putting a call to CpuDeadLoop() someplace maybe near where you want to start debugging. Then once attached to dbg, set the `Index` variable to 1 to continue. -- Rebecca _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
