42

What is the most likely causes of signal 11, also know as "segmentation fault"?

kubanczyk
  • 13,982
jpmartins
  • 1,514
  • 1
    -1 Seems like an answer not a question... – Scott Lundberg Sep 22 '09 at 01:50
  • 1
    If you want to make an info type post, it is better if you work on writing a good question.

    http://meta.stackexchange.com/questions/17463/ http://meta.stackexchange.com/questions/12513/

     – Zoredache Sep 22 '09 at 05:45
  • Accepted my own answer. I do not remember what I was thinking back in 2009 when I asked a question and answered it few minutes later. Probably I did not knew the answer, and asked before googling it... – jpmartins Aug 02 '19 at 19:25

2 Answers2

68

Signal 11 (SIGSEGV, also known as segmentation violation) means that the program accessed a memory location that was not assigned to it.

That's usually a bug in a program. So if you're writing your own program, that's the most likely cause.

It can also commonly occur with some hardware malfunctions.

kubanczyk
  • 13,982
jpmartins
  • 1,514
  • 7
    This is such an informative answer, why would it get 4 negative votes? (the reason it's only -3 is because I just upvoted it). – user1271772 Jun 23 '19 at 22:24
  • 2
    Got an upvote from me. What is the reason really for these negative votes?!! – Farzan Aug 01 '19 at 15:36
  • I usually see segmentation faults as the catch-all error in low-level languages. Tools like {Address|Leak}Sanitizer, as well as debuggers such as GDB, can help to demystify the error and point to a cause. – Matt F. Jul 03 '21 at 19:25
8

Please refer to segmentation fault on linux/unix

Ali Mezgani
  • 3,860