User Name Password Register
DaniWeb IT Discussion Community
All
What is DaniWeb IT Discussion Community?
You're currently browsing the *nix Hardware Configuration section within the Tech Talk category of DaniWeb, a massive community of 456,429 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,626 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our *nix Hardware Configuration advertiser: Lunarpages Linux Web Hosting
Views: 2013 | Replies: 0
Reply
Join Date: Sep 2004
Posts: 3
Reputation: arvind is an unknown quantity at this point 
Rep Power: 0
Solved Threads: 0
arvind arvind is offline Offline
Newbie Poster

Question Unix Memory Management.

  #1  
Jun 14th, 2007
hi there... im relatively new to the world of unix and to the Dani Web community too...

I am interested in the memory management techniques followed in the UNIX OS.

when i read thru a document related to that i came upon a paragraph, which im not able to decipher... this is regarding the concept of Virtual Memory.... the following is the subject...

"We saw that some virtual memory sections aren't mapped to physical memory. While some of them were simply paged out, others were never allocated by the process. When a process runs, its virtual memory table is small. As it allocates more memory pages, the table grows. However, if the process tries to access a virtual memory address of a section it hasn't allocated yet, the operating system has no where to bring this page from. The designers of the Unix system decided that this situation indicates a program bug, and thus instead of making an automatic allocation of a memory page in such a case, they chose to send a signal to the process. This signal is a SEGV signal (or SIGSEGV), and its default signal handler prints out a "Segmentation violation - core dumped" message, and dumps the memory image of the process into a file named 'core' in the process's current directory."

It will be easier if this is explained with some real time scenarion...
I need some light thrown upon this subject.. So any person who is ready to help me is invited... I wud also request upon some authoritative sources from where i can gain knowledge on this subject....

Eagerly awaitin a reply for the same....
AddThis Social Bookmark Button
Reply With Quote  
Reply

Only community members can participate in forum threads. You must register or log in to contribute.

DaniWeb *nix Hardware Configuration Marketplace
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

 

Thread Tools Display Modes

Similar Threads
Other Threads in the *nix Hardware Configuration Forum

All times are GMT -4. The time now is 1:26 am.
Forum system based on vBulletin Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
©2003 - 2008 DaniWeb® LLC