|
ru.linux
- RU.LINUX ---------------------------------------------------------------------
From : Valery Shishkov 2:5040/9 22 Sep 2001 17:07:28
To : Alexander Stavitsky
Subject : Re: Memory test
--------------------------------------------------------------------------------
>>>>> "AS" == Alexander Stavitsky wrote:
VS> Пересобрaть ядро. Вполне серьёзно. Если gcc вылетит с воплями 'signal
VS> 11', тогдa aтaс... :(
AS> Haвеpное всеже SIGILL 4... ;) Только это было aктуaльно для ПРОЦОВ
AS> (paзогнaнных), a не для пaмяти... А SIGSEGV мaло о чем (без gdb)
AS> может скaзaть.
Всё же SIGSEGV. Вот выдерка из GCC-HOWTO
===============================================================================
Internal compiler error: cc1 got fatal signal 11
Signal 11 is SIGSEGV, or `segmentation violation'. Usually it means
that the program got its pointers confused and tried to write to
memory it didn't own. So, it could be a gcc bug.
gcc is however, a well tested and reliable piece of software, for the
most part. It also uses a large number of complex data structures, and
an awful lot of pointers. In short, it's the pickiest RAM tester
commonly available. If you can't duplicate the bug --- if it doesn't
stop in the same place when you restart the compilation --- it's
almost certainly a problem with your hardware (CPU, memory,
motherboard or cache). Don't claim it as a bug because your computer
passes the power-on checks or runs Windows ok or whatever; these
`tests' are commonly and rightly held to be worthless. And don't claim
it's a bug because a kernel compile always stops during `make zImage'
--- of course it will! `make zImage' is probably compiling over 200
files; we're looking for a slightly smaller place than that.
==============================================================================
--
// WBR, Valery
--- Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.1 (Cuyahoga Valley)
* Origin: --== Illusory Town ==-- (2:5040/9.0)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
|
