https://wiki.sarg.dev/index.php?action=history&feed=atom&title=Code_segmentCode segment - Revision history2026-06-22T21:36:18ZRevision history for this page on the wikiMediaWiki 1.44.2https://wiki.sarg.dev/index.php?title=Code_segment&diff=624930&oldid=previmported>Theki at 13:02, 31 October 20242024-10-31T13:02:34Z<p></p>
<p><b>New page</b></p><div>{{Short description|Portion of an object file containing executable instructions}}<br />
[[File:Program memory layout.svg|thumb|383x383px|This shows the typical layout of a simple computer's program memory with the text, various data, and [[call stack|stack]] and [[heap (programming) |heap]] sections.]]<br />
<br />
In [[computing]], a '''code segment''', also known as a '''text segment''' or simply as '''text''', is a portion of an [[object file]] or the corresponding section of the program's [[virtual address space]] that contains [[executable]] [[instruction (computer science)|instructions]].<ref name="jason">{{Cite web<br />
| url = http://www.cs.uwm.edu/classes/cs315/Bacon/Lecture/HTML/ch10s04.html<br />
| title = Chapter 10. Subprogram Calls and the Stack<br />
| at = Section 10.4. Memory Segments<br />
| date = 2012-03-13<br />
| accessdate = 2014-05-02<br />
| author = Jason W. Bacon<br />
| website = cs.uwm.edu<br />
| archive-date = 2014-05-02<br />
| archive-url = https://web.archive.org/web/20140502115622/http://www.cs.uwm.edu/classes/cs315/Bacon/Lecture/HTML/ch10s04.html<br />
| url-status = dead<br />
}}</ref><br />
<br />
==Segment==<br />
The term "segment" comes from the [[memory segment]], which is a historical approach to [[memory management]] that has been succeeded by [[paging]]. When a program is stored in an object file, the code segment is a part of this file; when the [[Loader (computing)|loader]] places a program into [[main memory|memory]] so that it may be executed, various memory regions are allocated (in particular, as pages), corresponding to both the segments in the object files and to segments only needed at run time. For example, the code segment of an object file is loaded into a corresponding code segment in memory.<br />
<br />
The code segment in memory is typically read-only and has a fixed size, so on [[embedded system]]s it can usually be placed in [[read-only memory]] (ROM), without the need for loading. If the code segment is not read-only, then the particular [[computer architecture|architecture]] allows [[self-modifying code]]. Fixed-position or [[position-independent code]] may be shared in memory by several processes in segmented or paged memory systems.<ref name="jason"/><ref>{{Cite web<br />
| url = http://www.beingdeveloper.com/memory-layout-of-a-program/<br />
| title = Code Segment and Data Segment: Memory Layout of a Program<br />
| date = 2012-09-20<br />
| accessdate = 2014-05-02<br />
| author = Kai Wang<br />
| website = beingdeveloper.com<br />
| archive-date = 2014-05-02<br />
| archive-url = https://web.archive.org/web/20140502121214/http://www.beingdeveloper.com/memory-layout-of-a-program/<br />
| url-status = dead<br />
}}</ref> As a memory region, the code segment may be placed below the heap or stack in order to prevent [[Heap overflow|heap]] and [[stack overflow]]s from overwriting it.<ref>{{Cite conference<br />
| doi = 10.1109/ISCIT.2005.1567023<br />
| title = Buffer overflow protection based on adjusting code segment limit<br />
| conference = IEEE International Symposium on Communications and Information Technology<br />
| date = October 2005 <br />
| author1 = Yu-An Tan | author2 = Ji-yan Zheng | author3 = Yuan-Da Cao | author4 = Xue-lan Zhang<br />
| publisher = [[IEEE]]<br />
}}</ref><br />
<br />
== See also ==<br />
{{Portal|Computer programming}}<br />
* [[.bss]]<br />
* [[Data segment]]<br />
<br />
== References ==<br />
{{Reflist}}<br />
<br />
[[Category:Executable file formats]]<br />
[[Category:Memory management]]</div>imported>Theki