Re: (request) grub2 v1.97 how to debug and what is the real implement of b->allocate_pages.

[Phillip Susi <psusi@ubuntu.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/26/2012 10:34 PM, cr os wrote:
> Dears, I'm pulzzed with some problems when reading grub2 v1.97
> source code. Could you please help me?
> 
> Q1: About grub2 debug. Where does the grub2 log file(exist?)
> locate? Such as grub_dprintf, grub_fatal, grub_error function
> calls. Grub2 is a bootloader, it will load OS later, so the file
> system still not ready for grub2 creating a log file at that time,
> does it? Then how to debug grub2?

There is no log file; you set the debug variable to cause the messages
to be printed to the screen ( or serial console if you are using that ).

> Q2: About efi_call_4 function call. For an example, grub2 v1.97,
> in grub2\kern\efi\mm.c  grub_efi_allocate_pages function: 
> efi_call_4 (b->allocate_pages, type, GRUB_EFI_LOADER_DATA, pages,
> &address); I couldn't find the real function define of the pointer 
> "b->allocate_pages", what will be call after the efi_call_4(as
> below) function been called?

I haven't looked at the code in question but from the sound of it, you
are talking about calling one of the EFI system functions provided by
the system firmware.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQtQy+AAoJEJrBOlT6nu75HQoH/AjSqrTU8GFmQAL3pgCCj9YQ
m6jBg9S3NFbRRggkQEGuaLWL0FTtfxn/2b4Y+IKubp4V4IRCxvEeEorJfvc5KmhF
xDK/bnDlxsJtX7Ldzk1VezCmOzwAzK6pkR4mhIO/p85JarJyUOF5OPPHfY64H8eP
0X0pgOX5v49/j1yHVTcbZhAKrhgTrsieamsJjrQ2PxEVR+XR3Ee1TowpwN8ewoqW
9+fSs1oFCHKeCFY905poOb4KAsvFr6kpR+0hbiwoie5iy36YdKZ7OuL1SM1pq/gw
c8g4KgfbL8w6crXJ2hi7pTWqV0LOLWOcmu9wH0Gd15F7H5GzPxXeSYXJTxpuALw=
=hlUG
-----END PGP SIGNATURE-----