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 7656403
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T12:45:16+00:00 2026-05-31T12:45:16+00:00

When I run valgrind on this function, it says I’ve definitely lost 4 bytes.

  • 0

When I run valgrind on this function, it says I’ve definitely lost 4 bytes. I know it’s because I’m redirecting the pointer x in x=y, thus losing access to the initial memory allocated in the first line. How do I fix this? What’s the correct principle here? I’m just learning C, so I’m trying to get the hang of all this. Thanks!

int main() {
  int* x = malloc(sizeof(*x));
  int* y = malloc(sizeof(*y));
  *x = 2;
  *y = 5;
  x = y;
  *y = 6;
  *x = 4;
  printf("y = %d\n", *y);

  free(x);
  free(y);

  return 0;
}
  • 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-31T12:45:17+00:00Added an answer on May 31, 2026 at 12:45 pm

    x was pointing to an int, then that address was overwritten by x = y; (as you expected) but the space that the previous address pointed to was not released. x and y then contain the same address and therefore both point to the same space in memory, thus your free() calls are both trying to free the same location.

    If you don’t want to leak those 4 bytes, put in free(x); just before x = y;

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

Sidebar

Related Questions

I know this is platform-specific question, however, I would like to do some run-time
gcc 4.6.2 c89 I am passing a pointer to a function. This pointer will
I'm trying to install valgrind on os x (snow leopard/10.6.3). When I run the
I'm having some issues where when if I run this C extension outside of
I'm following 'Learn C the Hard Way', specifically the chapter on Valgrind . This
I'm quite lost on this one and I hope someone here could help. My
This is more focused than my previous Valgrind question; I am trying to narrow
If you've used Memcheck (from Valgrind) you'll probably be familiar with this message... Conditional
I have a big program to run. Using valgrind it takes hours and hours
Is this possible at all and how? Update: I need this because I create

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.