Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6634103
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T22:53:27+00:00 2026-05-25T22:53:27+00:00

Someone please clarify what happens with pointers after a fork(). As I understand it,

  • 0

Someone please clarify what happens with pointers after a fork().

As I understand it, pointers to anything on the stack or statically allocated are relative to the stack/data segment registers, so copying them exactly during a fork is OK.

However, what happens if I malloc() something before forking? for example:

void* p = malloc(64);
// put something in *p;
fork();

// what happens to p and the memory i allocated here?

possibilities I am thinking of:

  1. *p is copied to some other part of the heap, p is updated to reflect the newly copied location.

  2. p still points to the original. if any child runs free(p); the parent may be unable to access it.

  3. p still points to the original data, but the child process does not have rights to access/manage the memory.

which of these, if any, is correct?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T22:53:28+00:00Added an answer on May 25, 2026 at 10:53 pm

    When forking, child process becomes a copy of its parent. That includes any dynamically allocated memory. So the memory will be copied. Pointer address will stay the same (copy doesn’t change data, remember?), which is achieved by virtual addressing. Don’t forget to call free in both parent and child processes.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm not able to understand the following multi-dimensional code. Could someone please clarify me?
Possible Duplicate: What exactly does database normalization do? Can someone please clarify data normalization?
Can someone please clarify using a SIMPLE user story the full slice of what
Can someone please explain how to understand a logcat from an android force close.
Could someone please recommend a simple (as in very easy to understand) charting library
Bundle Name, Executable Name, Product Name... any more?? can someone please help clarify the
Can someone please clarify the following; if a have the following model; presentation-->slide-->video where
Could someone please clarify for me the semantic difference between these two: self.foo =
Could someone please clarify what the code means: public abstract class BaseJobProcessor<T> : JobProcessor
Can someone please help to clarify? Also, please mention if there are other representation

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.