Jump to content

Clover General discussion


ErmaC
30,136 posts in this topic

Recommended Posts

I released 5132 even if it is not final.

 

@Jief_Machak

I can't start gdb because of GCC compilation?

++ '[' 61 -le 60 ']'
++ '[' 61 -ge 60 ']'
++ echo Cannot find '"Clover : Image base = "' in /Users/sergey/src/CloverBootloader/Qemu/serial0_qemu_out.log after 60 seconds
Cannot find "Clover : Image base = " in /Users/sergey/src/CloverBootloader/Qemu/serial0_qemu_out.log after 60 seconds
++ exit 1
iMac2017:CloverBootloader sergey$ 

And the new bug, type F7 in the GUI

 

Снимок экрана 2021-03-28 в 13.58.49.png

Link to comment
Share on other sites

F7 ! Don’t even know what’s it’s for :lol:

Yes I’ll try.

 

for gdb, I think it should look for “CloverX64 : image...” instead of “Clover : Image...”. I’ve updated the scripts recently. Is it the last version ?

I’ll try when I’ll be back home in an hour or so.

Link to comment
Share on other sites

I resolved both issue.

1. For F7 there was no empty check.

2. For debug I have to compile with DEBUG_ON_SERIAL_PORT. Else no serial_...log

 

And one more. Returning to missing debug.log.

OC at start rewrite something and then debug log cancels to save.

Our DebugLog(DebugMode, ...) is not same as OC's DEBUG((DebugMode, ...)). There are different flags.

 

Committed.

I did this!

GNU gdb (GDB) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin17.7.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
./Qemu/CLOVERX64.debug: No such file or directory.
Remote debugging using localhost:9000
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
0x000000007f5143c7 in ?? ()
Hardware read watchpoint 1: *0
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 2 (panic_) pending.
Continuing.

 

But why ?

./Qemu/CLOVERX64.debug: No such file or directory.

It is here!

Link to comment
Share on other sites

Yes you need the serial debug to get the message stating the memory address.

after start, you need the Cliverx64.debug as well as the Cliverx64.efi.

.debug contains all symbols. Efi contains the executable.

best way is to start gdb_launch without any parameters : it’ll get the clover from the build folder. 

Link to comment
Share on other sites

Yes, it is better


For help, type "help".
Type "apropos word" to search for commands related to "word".
Reading symbols from /Users/sergey/src/CloverBootloader/Qemu/../Build/Clover/DEBUG_GCC53/X64/CLOVERX64.debug...
Remote debugging using localhost:9000
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: 
0x000000007f5143c7 in ?? ()
Hardware read watchpoint 1: *0
Breakpoint 2 at 0x66be9: file /Users/sergey/src/CloverBootloader/rEFIt_UEFI/Platform/Posix/abort.cpp, line 35--Type <RET> for more, q to quit, c to continue without paging--
.
Continuing.

What is the installation error?

Link to comment
Share on other sites

It's because of python. Some support files are missing for python. But we don't need it for Clover debugging.

55 minutes ago, Slice said:

But why ?


./Qemu/CLOVERX64.debug: No such file or directory.

It is here!

Script updated. Should work now.

I must admit I always use it with no parameter so gdb_launch go get CloverX64 from "./Build/Clover/DEBUG_GCC53/X64/". Works now with all path, absolute and relative.

1 hour ago, Slice said:

OC at start rewrite something

I only start OC in StartLoader(). How come OC could write something even before Clover ?

Link to comment
Share on other sites

By the way, for information, printing "DBG("CloverX64 : Image base = 0\n");" won't do anything because the address (0 in that case) is wrong and gdb won't be able to break, print stack trace or anything.

By doing that, gdb will still launch and we'll be misled about the origin of the problem.

Link to comment
Share on other sites

Compare timings in debug logs

from 25.02.2021

2:489  0:000  === [ GetAcpiTablesList ] =======================
2:493  0:004  Get Acpi Tables List from RSDT:
2:493  0:000   - [00]: FACP  A M I len=132
2:493  0:000   - [01]: APIC  A M I len=132
2:493  0:000   - [02]: FPDT  A M I len=68
2:493  0:000   - [03]: MCFG  A M I len=60
2:493  0:000   - [04]: FIDT  A M I len=156
2:493  0:000   - [05]: SSDT  A M I len=12628
2:493  0:000   - [06]: SSDT  A M I len=9540
2:493  0:000   - [07]: HPET  A M I len=56
2:493  0:000   - [08]: SSDT  A M I len=3643
2:493  0:000   - [09]: SSDT  A M I len=10967
2:493  0:000   - [10]: UEFI  A M I len=66
2:493  0:000   - [11]: SSDT  A M I len=3806
2:493  0:000   - [12]: LPIT  A M I len=148
2:493  0:000   - [13]: WSMT  A M I len=40
2:493  0:000   - [14]: SSDT  A M I len=671
2:493  0:000   - [15]: SSDT  A M I len=12290
2:493  0:000   - [16]: DBGP  A M I len=52
2:493  0:000   - [17]: DBG2  A M I len=84
2:493  0:000   - [18]: VFCT  A M I len=60548
2:493  0:000   - [19]: DMAR  A M I len=168
2:493  0:000  Calibrated TSC Frequency = 2712378910 = 2712MHz

And now

11:876  0:107  === [ GetAcpiTablesList ] =======================
11:979  0:103  Get Acpi Tables List from RSDT:
12:241  0:262   - [00]: FACP  A M I len=132
12:358  0:116   - [01]: APIC  A M I len=132
12:458  0:099   - [02]: FPDT  A M I len=68
12:558  0:100   - [03]: MCFG  A M I len=60
12:658  0:099   - [04]: FIDT  A M I len=156
12:758  0:100   - [05]: SSDT  A M I len=12628
12:858  0:100   - [06]: SSDT  A M I len=9540
12:958  0:099   - [07]: HPET  A M I len=56
13:058  0:099   - [08]: SSDT  A M I len=3643
13:158  0:100   - [09]: SSDT  A M I len=10967
13:258  0:100   - [10]: UEFI  A M I len=66
13:442  0:183   - [11]: SSDT  A M I len=3806
13:540  0:098   - [12]: LPIT  A M I len=148
13:649  0:108   - [13]: WSMT  A M I len=40
13:748  0:099   - [14]: SSDT  A M I len=671
13:840  0:091   - [15]: SSDT  A M I len=12290
13:932  0:091   - [16]: DBGP  A M I len=52
14:023  0:091   - [17]: DBG2  A M I len=84
14:115  0:091   - [18]: VFCT  A M I len=60548
14:206  0:091   - [19]: DMAR  A M I len=168
14:298  0:091  Calibrated TSC Frequency = 2712390070 = 2712MHz

It is a proof the debug log closed every line and this was not happened before. 

Link to comment
Share on other sites

@eng_redaesm

1 hour ago, eng_redaesm said:

both boots was unsuccessful,

Yes, you have to tell me because I thought the last commit wasn't working and the previous WAS working. So maybe the mistake is NOT in the last commit but a bit earlier.

Let's find out.

This : https://github.com/jief666/CloverCommits/blob/master/C-20210328085715-dc17de7.efi, should work. It's the same you confirmed working after you helped me find the problem with KernelPM and KPAppleIntelCPUPM.

If it's working, send me the log so I have a working base to compare to and find what have (wrongly) changed.

If it's working, try the next one here https://github.com/jief666/CloverCommits and tell me too.

Link to comment
Share on other sites

×
×
  • Create New...