From: "D. Deryl Downey" Date: 2013-03-12T05:30:07+09:00 Subject: Re: Segmentation fault while compiling ruby 1.9.3p392 with OpenSSL 1.0.1e installed This is a multi-part message in MIME format. --------------090004090201030003000708 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit SIG11 is not _usually_ a hardware error, though it can be related to memory issues. A SIG11 can be thrown when something tries to read or write to a memory area it doesn't have permissions on OR when it does and the area is corrupt. (Usually caused when memory cells have gone bad on individual sticks). Also happens when the addresses on the stack have become corrupt, again usually due to bad cells on the/a memory stick. The main issue though is that the pointer to a memory location is invalid. Run up against this so many times over the last 15+ years of computing, its not funny. In *some* cases, swapping out memory sticks has solved the issue. *That being said*, the most common issue that raises SIG11s are bugs in programs. (Bad pointer math, etc) There is no real way, short of testing your individual memory sticks in a hardware based memory tester (not something like mem86+ or Microscope), to determine if its specifically your memory or a bug in the software. There are subsystems that can throw this, hardware based, like overclocking memory and/or CPUs. However, the vast majority of SIG11s thrown are due to bugs in programs, not hardware. Just don't totally discount hardware, is the point. > Robert Klemme > March 11, 2013 3:58 PM > > Signal 11 is SIGSEGV (segmentation fault). That has nothing to do > with hardware - unless you want to suggest that the MMU is involved in > the process. This typically happens when dereferencing null pointers. > > Piotr, I'd start with simpler options - typically you do not need the > sudo's for configuring and compiling. Also I'd omit the architecture > unless you are cross compiling. > > ./configure --prefix=/usr/local/ > make > sudo make install > > Kind regards > > robert > > Miroslaw Niegowski > March 9, 2013 12:35 PM > > Hi, > signal 11 suggests a hardware error and is not related to software. I > would check ram first. > -- D. Deryl Downey "The bug which you would fright me with I seek" - William Shakespeare - The Winter's Tale, Act III, Scene II - A court of Justice. --------------090004090201030003000708 Content-Type: multipart/related; boundary="------------030209040208030502070506" --------------030209040208030502070506 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit SIG11 is not _usually_ a hardware error, though it can be related to memory issues. A SIG11 can be thrown when something tries to read or write to a memory area it doesn't have permissions on OR when it does and the area is corrupt. (Usually caused when memory cells have gone bad on individual sticks). Also happens when the addresses on the stack have become corrupt, again usually due to bad cells on the/a memory stick. The main issue though is that the pointer to a memory location is invalid.

Run up against this so many times over the last 15+ years of computing, its not funny. In *some* cases, swapping out memory sticks has solved the issue.

*That being said*, the most common issue that raises SIG11s are bugs in programs. (Bad pointer math, etc) There is no real way, short of testing your individual memory sticks in a hardware based memory tester (not something like mem86+ or Microscope), to determine if its specifically your memory or a bug in the software. There are subsystems that can throw this, hardware based, like overclocking memory and/or CPUs.

However, the vast majority of SIG11s thrown are due to bugs in programs, not hardware. Just don't totally discount hardware, is the point.





March 11, 2013 3:58 PM

Signal 11 is SIGSEGV (segmentation fault). That has nothing to do
with hardware - unless you want to suggest that the MMU is involved in
the process. This typically happens when dereferencing null pointers.

Piotr, I'd start with simpler options - typically you do not need the
sudo's for configuring and compiling. Also I'd omit the architecture
unless you are cross compiling.

./configure --prefix=/usr/local/
make
sudo make install

Kind regards

robert

March 9, 2013 12:35 PM

Hi,
signal 11 suggests a hardware error and is not related to software. I would check ram first.


--
D. Deryl Downey

 "The bug which you would fright me with I seek" - William Shakespeare - The Winter's Tale, Act III, Scene II - A court of Justice.
--------------030209040208030502070506 Content-Type: image/jpeg; x-apple-mail-type=stationery; name="postbox-contact.jpg" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="postbox-contact.jpg" /9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAMCAgICAgMCAgIDAwMDBAYEBAQEBAgGBgUGCQgK CgkICQkKDA8MCgsOCwkJDRENDg8QEBEQCgwSExIQEw8QEBD/2wBDAQMDAwQDBAgEBAgQCwkL EBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBD/wAAR CAAZABkDAREAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDyDxTp+p6n4i0vWdY1W3vbvVWs7q9u73TL eaSWZ1iJ3O6kncxOBkBQMDAUAdlScacbsyo0pYqXLHQ9O+L2mfCjxVpOseNPDer6Z/bNsyRv jTrC8smlEAVYm2xiVM4B3HIDZzwMVxrFShL3loyKeExSnZWkuvc4j4E6zfWmkePtN1LSLGzm l07T1We1sLaIpm6UsUkjXd0xhhgg8gggV2wlGtG5Vam8PV5epzH/AA1N+0F/0V3WP+/cH/xN Z3gXaRo/FHSNV1q38I6V4bia5v54YJkgERPnFIEwoH8RPPHbNPEQ54prYzw2Kp0k5ydkcPrf hrxz4fsVvL3ws2j2upKz4W6XNwduciMEsRjknHArjdOVveR24TN8NOt7OlJHrHwe0bxbd/D+ 4n0q2stWk1GzghS0t7hTexbboli0P324CkYByCPSrwtSMU4XObHyk6rm1p3PHf8AhCPHv/Qj 3/8A4By//E1tyruzn+tQ7o9l1PXpNV8O2X9r6XJa6rpttHB9stZJLS5t3WNY5FbHQ5UhgADk EGvMlXq/BfQ5Pa++7pM5610fxb4jUeG9FvdQ1KfT7SaOGa6KObG3kXaQHYAqPmIySMc0/rVS MbMzUKSqe1Ubeh1/gDTvhr8KYdNubbS7jXPFFifPnvpL6VbW2kBztRUKqwHrg5NcseaU+Z6I 7a2Z1aq9m3p2Oa/4Sfxp/wBG/X//AIBX1erePma+zo/ylD9rf/k4Dx3/ANfy/wDomOuaXxGE t2ea6F017/cX+ZrN9A6Gh8KP+SjeGf8AsN2P/o9KtbkL4j9m63Oo/9k= --------------030209040208030502070506 Content-Type: image/jpeg; x-apple-mail-type=stationery; name="compose-unknown-contact.jpg" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="compose-unknown-contact.jpg" /9j/4AAQSkZJRgABAQEARwBHAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEC AQEBAQEBAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/2wBDAQEBAQEBAQICAgICAgIC AgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/wAAR CAAZABkDAREAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAABgcICQr/xAA0EAABAwMCAgUK BwAAAAAAAAACAQMEBQYRABITIQcUMUF2CBUXIjI2N0JRtVRWkZOV0dL/xAAYAQEAAwEAAAAA AAAAAAAAAAADAAEEAv/EACQRAAICAAQGAwAAAAAAAAAAAAABAhEDMrHREyExM0FxgfDx/9oA DAMBAAIRAxEAPwDuEt+gW/ULet6oVC3rfqNQqFv0OfPn1GhUqfOmzZtKZlS5UqZMaNwzNwiJ VIl7eXLCaZIGwBl3TY8epPx2+jy2ZNPjvkwc9uhW8j7nCPhvOsQliYIeS7cvCpp8o50qwrC4 v3lsNSDbdmTEhvs2tahxpfV3WnmbbozJEw/gwdadbYExVRXKEKoSdvJcaOSqxE7/AAiX0gXx +a69/JSf9alIlste0VzaNpeFrcT9KKymotyiaZ0KRCnzacoE7Kjzn4gi2KqUh3jqDHDHv4mR UfruTWlMzlVUKIVNp9GguEJnAh0+IZjyAiisgyRDnu5azS8miKqjOTVkKqS/psG37fo1Fbab eg25b8eZPeFJBBJSjMG5HjMeyihnaauZwe4OGiju13GAcpOwBeN+U8/IkGbsiS8b7ryogmbz hbyc9REROfZhERO5ETShjPtvpGqTUyLErytS4siSwx5x2tRH4hPOI0DkjZtaJtFxuVEbIUUi yeNujlBUJGbJN6nM/Cyf2Hf60YgjvKA+NPSP4gT7axpcPtr51YWJnYn9dnAQWl722p4ot37y zqnlfp6FrqbwawG8/9k= --------------030209040208030502070506-- --------------090004090201030003000708--