Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option for increasing rom size #5

Open
DrRamm opened this issue Jan 5, 2020 · 1 comment
Open

Option for increasing rom size #5

DrRamm opened this issue Jan 5, 2020 · 1 comment

Comments

@DrRamm
Copy link

DrRamm commented Jan 5, 2020

By default IDA suggest ROM size as Loading size, but it's not good. Better increase ROM size for handling virtual values, which in case ROM == Loading show as red. Increasing ROM size will help to get rid of that.

@marin-m
Copy link
Owner

marin-m commented Jan 5, 2020

Hello,

vmlinux-to-elf does not create a "ROM section", but rather a .bss section (made of empty bytes) of fixed size in the generated ELF file. See: https://github.com/marin-m/vmlinux-to-elf/blob/d7f926d/vmlinux_to_elf/elf_symbolizer.py#L84

By default, this section starts right after a .kernel section (which contains the code and initialized data of the kernel, from the input file), and is of a size of 0x100000 (1 MB).

Can you please specify more the case that you encountered:

  • Did you encounter references to data whose the addressing was located far outside of the .kernel and .bss sections, or
  • Did you encounter references to data that was located somewhat after the end of the automatically created .bss section?

Using a command such as readelf -aW or objdump -x over the generated ELF file may be useful to you to analyze the layout of the generated file.

Thank you,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants