This forum has been archived. All content is frozen. Please use KDE Discuss instead.

What causes a SIGSEGV # 11?

Tags: None
(comma "," separated)
S4SQU4TCH
Registered Member
Posts
6
Karma
0

What causes a SIGSEGV # 11?

Tue Dec 29, 2009 7:14 pm
What can cause a SIGSEGV # 11? Is it normally attributed to one issue? Is there a way to tell kdenlive to ignore a SIGSEGV rather than terminating?
eriksl
Registered Member
Posts
32
Karma
0

Re: What causes a SIGSEGV # 11?

Fri Jan 01, 2010 1:09 pm
Signal 11 is segmentation fault. This means the program is trying to access memory (or I/O ports) it doesn't have permission for. This is to prevent applications from messing up other applications or even the operating system. The signal can be "caught" and "ignored", but most of the time that won't buy you much, because it really indicates a serious error that the application cannot recover from.

The most common cause for a segmentation fault is simply a bug in the application, dereferencing a null pointer being favorite. Far less common causes are: dynamic library version mis-matches, overheating of the cpu and kernel bugs. But as said, most of the time it's simply a bug.


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]