Tim Roberts

@phip1611 The PR template indeed didn't seem to get filled at the time, but I was running a -dev channel browser, so I'm assuming it was a rendering bug. I...

> @timrobertsdev The PR looks good now! Could you also run `cargo fmt` to fix the failing CI? All set.

I haven't found anything in the wild that still uses EFI < 1.10, but theoretically this would also affect any UEFI drivers or applications written without the use of `OpenProtocol`...

This stuff is indeed tricky! With UEFI switching between tasks with interrupts, I'm not sure how any kind of meaningful validation could be done. I'm very on-board with your recent...

I found [this article](https://xitan.me/posts/rust-uefi-runtime-driver/), but their approach doesn't seem to work. It finds the base address and address of each section, but still doesn't provide any symbols to gdb. Then...

The executable should be stripped, but applications built in C with EDK2 in `DEBUG` mode do output `.map` and `.pdb` files for debugging. Source: https://edk2-docs.gitbook.io/edk-ii-build-specification/12_build_changes_and_customizations/121_building_for_debug With that in mind, it...

Can confirm the above solution works, with the additional step of removing "is-builtin" from the target file. `build.py` would need to be updated to use the custom target as well....

Yeah, that's the same issue that I was having with the pdb files. I tested on both linux and windows(mingw) and was unable to correctly load any symbols. I'll give...

@no92 Nevermind, I got it working. The mistake I was making was attempting to run the `dbg` gdbscript while QEMU itself was halted and waiting for debugger, instead of the...

Update: Per Josh Triplett on the rustlang zulip, `extern "C"` on the "x86_64-unknown-uefi" target should be the proper UEFI ABI, so we can actually implement this, using `extern "C"` instead...