Driver
Re: Driver
maybe a bit more info could help .
I'm assuming VolTroX is your OS?
You need to make a relocatable file that you can fill in the unresolved function calls dynamically.
Please provide more information about how you would interface with your kernel and other base info.
Ask Smart Questions please.
I'm assuming VolTroX is your OS?
You need to make a relocatable file that you can fill in the unresolved function calls dynamically.
Please provide more information about how you would interface with your kernel and other base info.
Ask Smart Questions please.
Website: https://joscor.com
Re: Driver
im sorry if i am not very descrete, i have seen code where if you load a file to memory it stays there, is there a way i could use my filesystem to load it but not execute it, can i just call functions from the file loaded in memory?
hows that?
hows that?
Re: Driver
Two options that I know of:GhostXoPCorp wrote:im sorry if i am not very descrete, i have seen code where if you load a file to memory it stays there, is there a way i could use my filesystem to load it but not execute it, can i just call functions from the file loaded in memory?
-Use a linked list (or some sort) of function pointers to those functions in the loaded module, or
-Use a file format that supports dynamic linking (ie elf and pe).
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
- Troy Martin
- Member
- Posts: 1686
- Joined: Fri Apr 18, 2008 4:40 pm
- Location: Langley, Vancouver, BC, Canada
- Contact:
Re: Driver
I would sure as hell hope that your file loading calls are separate from your program execution calls.GhostXoPCorp wrote:is there a way i could use my filesystem to load it but not execute it
Re: Driver
i know i have to do that, alright i have found something, thanks for your time