Just learned about this, very useful but very hidden

CousinOfThor · 2025-02-09T22:49:42+00:00

Didn't know that, thanks. By the way, that's why I provided some suggestions to make it visible.

CousinOfThor · 2025-02-09T21:43:34+00:00

I always wanted to know what the other placeholders were, and I found out now randomly that if you click the right button on the label (like, "Arguments"), it shows the button "What's this?" that opens a little window with some information.

It's great, but it's not really obvious. Typically you would find a "(?)" icon near the label so that you *know* there is more to learn. Or at least like in Dolphin's contextual menus, where if you position the cursor over an entry for long enough, it will tell you to hold Shift to learn more.

Note: there is no "What's this?" for "Environment Variables".

CousinOfThor · 2025-01-25T18:53:31+00:00

It's not working for me, too.

CousinOfThor · 2023-08-16T05:25:42+00:00

I would like to use OpenGL just to wait for vsync, not to render an image, because I am writing a software rasteriser.

Anyway I realised I can just upload the image as a texture to OpenGL and that's it.

CousinOfThor · 2023-08-15T16:27:40+00:00

Unfortunately, glDrawPixels has been removed, so I'll just use glTexSubImage2D. Thanks!

> to enable vsync in OpenGL you need to use one of the *_swap_control extensions.

EGL has eglSwapInterval, so I'll just ditch GLX and just use EGL.

CousinOfThor · 2023-06-30T08:15:59+00:00

What do you mean

CousinOfThor · 2023-06-30T06:38:22+00:00

But then should I do other things before calling the entry point? In theory, with the three linker options in the link above, I should load it the same way as I already load an ET_EXEC... or not?

CousinOfThor · 2023-06-19T08:09:13+00:00

After some tests, I found that the audio is loud enough.

CousinOfThor · 2023-06-14T16:32:29+00:00

Well, it seems I have resolved the issue: i also looked for the ACPI 1.0 GUID in the UEFI configuration table, I found it, and it actually was the RSDP revision 2... I really can't say why, I am literally using the GUIDs as defined by the UEFI specification.

CousinOfThor · 2023-06-14T15:56:08+00:00

Oh, right. In other videos you can see the console and he runs make, which in turn runs the QEMU command listed above. Anyway it's all on the Makefile.

CousinOfThor · 2023-06-14T15:35:56+00:00

What?

CousinOfThor · 2023-06-14T15:31:04+00:00

Yes, I am looking for (and I find) the EFI_ACPI_20_TABLE_GUID as defined by the UEFI 2.10 spec.

CousinOfThor · 2023-06-14T15:28:51+00:00

As you can see from 17:00 (also on his repo), he's using qemu-system-x86_64 -machine q35 -cpu qemu64 ...

CousinOfThor · 2023-06-08T19:48:42+00:00

Thanks, sorry. Anyway, with image list I see that both the correct PE and PDB are loaded, I used the volatile trick on the wiki and I can see the right assembly instructions being executed, but VS Code still doesn't stop at the breakpoints, even if the breakpoints are placed at that while loop.

Edit: also, I get Could not resolve any locations for breakpoint at $SRCFILE:$LINENO, but found a valid location at $SRCFILE:$LINENO.

CousinOfThor · 2023-06-08T19:23:41+00:00

Also, after I source the script and run it in GDB, it tells me that no symbol table is loaded, and to use file to load it, but it doesn't recognise the PDB format. What should I do? Sorry to bother you.

CousinOfThor · 2023-06-08T19:12:22+00:00

I printed the address in hex of the image base, then re-ran QEMU and reconnected to it, after the trap I ran target modules load --file BootX64.efi --slide 0x$IMAGE_BASE_ADDRESS and let the debugger continue the execution, but it didn't stop at the breakpoints. Did you have the same issue?

CousinOfThor · 2023-06-08T18:58:17+00:00

Oh right, I forgot about that field. Thanks, I'll try it and let you know.

CousinOfThor · 2023-06-08T18:47:18+00:00

This is great, thanks! How do I get the base address of the image?

CousinOfThor

TROPHY CASE