What can cause segmentation faults in C++? [closed]

by

Segmentation fault is caused by bad accesses to memory, only if your OS has a MMU (Memory Management Unit). Otherwise, you won’t get it but only strange behavior.

The virtual memory (the entire memory accessible to you = 2^(sizeof(pointer_type)*8) (ie: 2^num_bits_in_pointer_type)) is mapped to physical memory in units named pages or segments (paging superseded segmentation but they are still used).

Each page has some protection rights, if you try to read from a page with no-read access you’ll get a segfault. If you try to write to a readonly location you’ll get a SIGSEGV.

If you have an unitialized pointer and use it it may happen that it will point to another good location so you’ll don’t get a segfault. If you have a small array reading after it’s bound may corrupt other memory areas if it doesn’t get past the page boundary.

Also, since there are many pages, not all of them are really mapped. If you touch a non-mapped page you’ll get a segfault. Actually, any access to a non mapped page will have to take into account copy on write, pages on swap, lazy loading, memory mapped files and other things. See this article on page fault handling, especially the second diagram there, posted here below too (but read the article for more explanations)

page fault handling
(source: champ at vistech.net)

You are mainly interested in what happens in user space and all paths leading to SIGSEGV. but kernel space is also interesting.

More Related Contents:

  1. CPP- I am getting Segmentation fault (core dumped)?
  2. Reading garbage instead of segfault for non-existant memory locations
  3. segmentation fault in an sorted linked list program for Homework [closed]
  4. I keep getting a segfault every time I run this program, but I cannot understand why
  5. Segmentation fault on large array sizes
  6. What is a segmentation fault?
  7. Definitive List of Common Reasons for Segmentation Faults
  8. Why don’t I get a segmentation fault when I write beyond the end of an array?
  9. cudaMemcpy segmentation fault
  10. Determine the line of code that causes a segmentation fault?
  11. How to catch segmentation fault in Linux?
  12. Fixing Segmentation faults in C++
  13. Segmentation fault at glGenVertexArrays( 1, &vao );
  14. SetJmp/LongJmp: Why is this throwing a segfault?
  15. Segfaults in malloc() and malloc_consolidate()
  16. Why is a segmentation fault not recoverable?
  17. Best practices for recovering from a segmentation fault
  18. Insertion sort stops working after million input
  19. Why the values {1, 1, 0, -1, -1, -1, 0, 1} and {0, 1, 1, 1, 0, -1, -1, -1} were chosen for dx[dir] and dy[dir]? [closed]
  20. AVX2 what is the most efficient way to pack left based on a mask?
  21. Is it better to use std::memcpy() or std::copy() in terms to performance?
  22. How do I get the index of an iterator of an std::vector?
  23. How to use std::sort to sort an array in C++
  24. Algorithm for finding the smallest power of two that’s greater or equal to a given value [duplicate]
  25. Why getline skips first line?
  26. Does returning a local variable return a copy and destroy the original(nrvo)?
  27. class & function names highlighting in Vim
  28. MSVC 2015 Universal CRT for app-local deployment
  29. Why the libc++ std::vector internally keeps three pointers instead of one pointer and two sizes?
  30. Seeking code stub generator (from header files) [closed]

Leave a Comment