Using pointer after free()

by

Because using an invalid pointer invokes undefined behavior. And that means that the behavior is… well… undefined. It’s not obliged to crash.

More Related Contents:

  1. what the output of this code and why?
  2. printf anomaly after “fork()”
  3. How to make child process die after parent exits?
  4. What is time_t ultimately a typedef to?
  5. What is the equivalent to Posix popen() in the Win32 API?
  6. How to recursively list directories in C on Linux?
  7. Why does this program print “forked!” 4 times?
  8. How does kernel get an executable binary file running under linux?
  9. Measure time in Linux – time vs clock vs getrusage vs clock_gettime vs gettimeofday vs timespec_get?
  10. stdout thread-safe in C on Linux?
  11. Is malloc/free a syscall or a library routine provided by libc?
  12. Signal handling with multiple threads in Linux
  13. Best way to invoke gdb from inside program to print its stacktrace?
  14. How to include needed C library using gcc?
  15. Unexpected exec permission from mmap when assembly files included in the project
  16. Whole one core dedicated to single process
  17. Finding out what the GCC include path is [duplicate]
  18. Bind failed: Address already in use
  19. Why do I have to define LD_LIBRARY_PATH with an export every time I run my application?
  20. Is there a macro definition to check the Linux kernel version?
  21. Writing to a closed, local TCP socket not failing
  22. Write to .txt file?
  23. Do forked child processes use the same semaphore?
  24. What’s a good C decompiler? [closed]
  25. How to set the IP address from C in linux
  26. In C, what’s the size of stdout buffer?
  27. What API do I call to get the system uptime?
  28. Where are syscalls located in glibc source
  29. multiple threads able to get flock at the same time
  30. How to know if a Linux system call is restartable or not?

Leave a Comment