https://bugzilla.novell.com/show_bug.cgi?id=740407
https://bugzilla.novell.com/show_bug.cgi?id=740407#c2
Jeff Mahoney changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Jeff Mahoney 2012-03-19 12:31:58 EDT ---
There seem to be a few misunderstandings here.
1) Signal 11 is how the kernel terminates a process when a Segmentation Fault
occurs. It's the most common way that *any* userspace software on a UNIX or
UNIX-like system will crash. It's not a "single" bug - it's *any* bug. I can
cause a segfault by doing something like:
int *p = NULL;
*p = 1; /* crash */
2) Saying you can reproduce a Seg Fault without providing any documentation for
it is not enough information to investigate a crash. The stack trace describes
the crash and is *essential* to finding the cause.
3) A crash in userspace software is almost always a defect in the userspace
software.[1] Even if the kernel used all the memory, which I doubt, an
application that can't handle ENOMEM is buggy. The application may be killed by
the kernel, but that would have an accompanying message in the kernel log.
4) Your image shows a completely normal system. The kernel will always use
unused memory for caches. Without attaching more evidence, like the contents of
/proc/meminfo, there's nothing to investigate here.
Closing as INVALID.
[1] The X server may be an exception, but this is typically due to faulty (or
misunderstood, in the case of some nVidia chips) hardware or a driver error in
the drm code. These can be identified by the backtrace.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
