Are .text sections shared between loaded executables?
When two instances of an executable are loaded, one after the other, and are running simultaneously, are the read-only .text
sections shared between their address spaces, like a shared library? Wouldn't they always be the exact same? I am only referring to the executable's object file, (ie. the one with the main()
function).
Is this behavior exhibited in Linux? If so, do other Unices do so as well?
If this is not done in Linux, would any benefit come from implementing executables that often run multiple instances in parallel as shared libraries, with the invoked executable simply calling a main function in the library?
kernel elf dynamic-loading
add a comment |
When two instances of an executable are loaded, one after the other, and are running simultaneously, are the read-only .text
sections shared between their address spaces, like a shared library? Wouldn't they always be the exact same? I am only referring to the executable's object file, (ie. the one with the main()
function).
Is this behavior exhibited in Linux? If so, do other Unices do so as well?
If this is not done in Linux, would any benefit come from implementing executables that often run multiple instances in parallel as shared libraries, with the invoked executable simply calling a main function in the library?
kernel elf dynamic-loading
Strictly speaking, it doesn't have to be shared. But in the real-life they are always shared because they're mmaping the same file region
– 炸鱼薯条德里克
Dec 31 '18 at 4:45
@炸鱼薯条德里克 Does the characteristic of mapping the same file region always lead to sharing in memory?
– novice
Jan 1 at 18:21
add a comment |
When two instances of an executable are loaded, one after the other, and are running simultaneously, are the read-only .text
sections shared between their address spaces, like a shared library? Wouldn't they always be the exact same? I am only referring to the executable's object file, (ie. the one with the main()
function).
Is this behavior exhibited in Linux? If so, do other Unices do so as well?
If this is not done in Linux, would any benefit come from implementing executables that often run multiple instances in parallel as shared libraries, with the invoked executable simply calling a main function in the library?
kernel elf dynamic-loading
When two instances of an executable are loaded, one after the other, and are running simultaneously, are the read-only .text
sections shared between their address spaces, like a shared library? Wouldn't they always be the exact same? I am only referring to the executable's object file, (ie. the one with the main()
function).
Is this behavior exhibited in Linux? If so, do other Unices do so as well?
If this is not done in Linux, would any benefit come from implementing executables that often run multiple instances in parallel as shared libraries, with the invoked executable simply calling a main function in the library?
kernel elf dynamic-loading
kernel elf dynamic-loading
edited 2 days ago
asked Dec 31 '18 at 3:28
novice
135
135
Strictly speaking, it doesn't have to be shared. But in the real-life they are always shared because they're mmaping the same file region
– 炸鱼薯条德里克
Dec 31 '18 at 4:45
@炸鱼薯条德里克 Does the characteristic of mapping the same file region always lead to sharing in memory?
– novice
Jan 1 at 18:21
add a comment |
Strictly speaking, it doesn't have to be shared. But in the real-life they are always shared because they're mmaping the same file region
– 炸鱼薯条德里克
Dec 31 '18 at 4:45
@炸鱼薯条德里克 Does the characteristic of mapping the same file region always lead to sharing in memory?
– novice
Jan 1 at 18:21
Strictly speaking, it doesn't have to be shared. But in the real-life they are always shared because they're mmaping the same file region
– 炸鱼薯条德里克
Dec 31 '18 at 4:45
Strictly speaking, it doesn't have to be shared. But in the real-life they are always shared because they're mmaping the same file region
– 炸鱼薯条德里克
Dec 31 '18 at 4:45
@炸鱼薯条德里克 Does the characteristic of mapping the same file region always lead to sharing in memory?
– novice
Jan 1 at 18:21
@炸鱼薯条德里克 Does the characteristic of mapping the same file region always lead to sharing in memory?
– novice
Jan 1 at 18:21
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491681%2fare-text-sections-shared-between-loaded-executables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491681%2fare-text-sections-shared-between-loaded-executables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Strictly speaking, it doesn't have to be shared. But in the real-life they are always shared because they're mmaping the same file region
– 炸鱼薯条德里克
Dec 31 '18 at 4:45
@炸鱼薯条德里克 Does the characteristic of mapping the same file region always lead to sharing in memory?
– novice
Jan 1 at 18:21