1MB Linker and GUI bugs?

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
User avatar
Octacone
Member
Member
Posts: 1138
Joined: Fri Aug 07, 2015 6:13 am

1MB Linker and GUI bugs?

Post by Octacone »

Could my linker be related to this? I just realized that my kernel is getting loaded at around 1MB barrier, like what!!! Can that make this weird bug appear?
I allocated 1GB to my OS, there should not be any problems with that right?
LinkerBug.png
This is my linker script:

Code: Select all

OUTPUT_FORMAT(elf32-i386)
ENTRY(Start)
SECTIONS
 {
   	. = 1M;
	Kernel_Physical_Address = .;
	.text : AT(ADDR(.text))
	{
		Text_Section_Physical_Address = .;
		*(.Multiboot)
		*(.Text)
	}
	.rodata ALIGN (0x1000) : AT(ADDR(.rodata))
	{
		Rodata_Section_Physical_Address = .;
		*(.rodata)
	}
	.data ALIGN (0x1000) : AT(ADDR(.data))
	{
		Data_Section_Physical_Address = .;
		*(.data)
	}
	.bss : AT(ADDR(.bss))
	{
		BSS_Section_Physical_Address = .;
		*(COMMON)
		*(.bss)
		*(.Bootstrap_Stack)
		Kernel_End = .;
	}
	Kernel_Heap_Start = .; 	
 }
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
User avatar
Ch4ozz
Member
Member
Posts: 170
Joined: Mon Jul 18, 2016 2:46 pm
Libera.chat IRC: esi

Re: 1MB Linker and GUI bugs?

Post by Ch4ozz »

This happened to me when I overwrote pictures etc which I passed that time as ramdisk with my own kernel because of grub simply loading it to a position I specified in the linkerscript without knowing that qemu loads ramdisks there.
But its your OS, we cant magically know why this bug happens if you dont even show a screenshot without the bug.
Post Reply