- Where Developers Learn, Share, & Build Careers


In many places there is no check for zero after the malloc or memalign in the small kernel boot loader.

For example: in

  zero to Flash_init (empty) flash_code = memalign (32, 1024); Char * target_cmdline (char * org_cmdline) {cmdline = (four *) Molk (MAX_CMDLINE_LEN); Memset (CMDline, 0, MAX_CMDLINE_LEN); }   

Is it supposed to return the malloc zero when booting?

shunty, you should probably do some code background research :)

Referring to the fact that Google / Qcom by the author of LK, and that part (aboot) is not created using some of the legacy Android bootloader dump, I still have files that look very similar but not published They can do it for the public domain

The reason they are not checking for zero is because the legacy bootloader was implemented as a very basic form in the heap, there was no free, no fragmentation, just allocated, pay address and forget that is the reason The pile was not used for a very long time, so there was no problem there, but in the LK itself which was capable of doing very much OS work in itself, this is just a simple mistake because heaps And supports other standard heap functions.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -