Dear Andrew,

Thank you for your detailed explanation regarding the behavior of symbol 
loading in GDB when debugging OVMF.

I just want to make sure I’ve understood your points correctly:

* 

*Symbol Loading Timing:* The issue I’m facing might occur because I’m 
connecting to GDB before all the necessary drivers or applications have been 
loaded. As a result, the symbols for these modules aren’t available at the time 
of connection, leading to breakpoints not being hit.

* 

*Pending Breakpoints:* You mentioned that it’s possible to set pending 
breakpoints in GDB, which will activate once the relevant symbols are loaded. 
However, this still requires some mechanism to ensure that the symbols are 
eventually loaded as the modules initialize.

* 

*Using CpuDeadLoop():* If I insert a CpuDeadLoop(); after the modules are 
loaded, I can connect GDB, ensure the symbols are loaded, and then step over 
the loop to continue debugging from that point.

Could you confirm if I’ve captured this correctly? Also, is using 
CpuDeadLoop(); the best approach to guarantee that all symbols are loaded 
before continuing the debugging process?

Thank you again for your insights!

Best regards,
Mahsa


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120412): https://edk2.groups.io/g/devel/message/120412
Mute This Topic: https://groups.io/mt/91279461/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to