23 / Ace / Taken by garlic bread / chaotic neutral code dipshit / Event Tech apprentice / Demoscene
| Pronouns | Any |
| Little Pony Horse | https://littlepony.horse |
| Muh Website | https://itsebu.net |
| Matrix | ebu:littlepony.horse |
Ebu, certified horse 
- 139 Followers
- 78 Following
- 463 Posts
That guy from Twitter!
23 / Ace / Taken by garlic bread / chaotic neutral code dipshit / Event Tech apprentice / Demoscene
23 / Ace / Taken by garlic bread / chaotic neutral code dipshit / Event Tech apprentice / Demoscene
Well, partially, provided the image gets loaded at a certain address. Would have to figure out a way to either always ensure the same load address, or (better) dynamically get the load address and then let lldb know about it. So far this seems like a chicken-and-egg kind of thing. I need to run it to know the location, but I can't run it without the location?
And as expected previously, CodeLLDB doesn't crash anymore, now that debug symbols are actually available, whooop!
Now just have to figure out how to get the image base address from OVMF
AutomataDogBrink at MFF23. Their group stopped by while we were taking photos, and I offered to snap a few for them. :)
#Furry #Furries #Fursuit #FursuitFriday #Photography #Anthro #MFF #MFF23
@ryze just thought about it again, but if the symbols were embedded in the actual binary then lldb should find them even without trying to load the pdb afterwards, which it also doesn't. Maybe gotta try the exact reverse and ask it to embed them explicitly, perhaps it can find them then
He there #rust users. I'm struggling with debugging a freestanding UEFI binary inside of QEMU, seems like lldb doesn't find any debugging symbols inside the generated .pdb files. Seems to be a known issue for gdb, but lldb apparently supports it? I would like to have symbols available, but none of the things I find online indicate that anyone else just isn't able to see any of the debugging symbols. Could this be because of #![no_std] perhaps? I don't really know where to look for any info on this, so any help is appreciated!
#rustlang #uefi #qemu
#rustlang #uefi #qemu
@ryze yeah, that's another option I've already tried. That was included while I used the debug = true option as well, so that split should have happened. lldb just ends up with num_symbols = 0 regardless when I try to list them sadly
In retrospect I'm not entirely sure anymore if I did it properly, I'll try this again just in case, but I'm pretty sure I did.
@ryze yeah, it's running in dev, tried setting debug = true explicitly as well in case something was funky, but didn't change anything about the result.
He there #rust users. I'm struggling with debugging a freestanding UEFI binary inside of QEMU, seems like lldb doesn't find any debugging symbols inside the generated .pdb files. Seems to be a known issue for gdb, but lldb apparently supports it? I would like to have symbols available, but none of the things I find online indicate that anyone else just isn't able to see any of the debugging symbols. Could this be because of #![no_std] perhaps? I don't really know where to look for any info on this, so any help is appreciated!
#rustlang #uefi #qemu
#rustlang #uefi #qemu