SuSE gcc blows up

[mmorin at schedsys.com (Massimo Morin)]

Hi guys,

ccb at valinux.com wrote:

> Fatal error 11 in gcc is usually an indication of a memory
> error.  Got Diagnostics?

I do not trully belive it is a memory problem. I got a lenghty discussion times
ago about it, here is

On Thu, 08 Jun 2000, Calvin Ostrum wrote:

> On Thu, 08 Jun 2000, Massimo Morin wrote:
> ....
> | This is very weird. I tought as well it was a memory problem, even if the
> | machine was working just fine before the upgrade to RH6.1
> |
> | LEt me ask: did you upgraded, or just suddenly the machine stopped  to work?
>
> Just suddently.  No change had been made.  I was in the middle of
> compiling for the first time a large program I had just downloaded
> and I associated it with that but I think it was an error to do so.
>
> | It wasn't a bad idea the fact that the memory went bad..... but I really do
> | not have any idea on what happend now
>
> What do you think of this idea: linux-zealots are always saying
> how wonderful Linux is, it never crashes, etc.  (If X crashes,
> thats just an application program!).  When it does crash, with
> a kernel panic like this one, they say, oh, thats your HARDWAREs
> fault.  Perhaps many of these cases it ISNT the hardwares fault??
>
> Here is one case for sure it isn't hardware fault all the time:
> "signal 11's".  Have you noticed a lot of people pontificating
> that signal 11's mean bad memory?  Completely untrue, of course.
> Signal 11's are just segmentation faults, and the usual thing
> that causes them is a bug in a program accessing nonexistent
> memory with a wonky pointer.
>
> Perhaps the same thing is the case here, and the kernel really
> did have problems.  I assume your Suse and RH kernels were not
> identical.  (If they were, they were installed in different
> overall systems that might have made a difference).
>
> I just ran memtest86 which is supposed to be a pretty good program,
> for 2 hours, through all its tests, including extended, and it
> found no problems with my memory.
>

As Calvin pointed out sometimes signal 11 is a plain signal for a bus error.
The disussion that he is mentioning is at
http://www.bitwizard.nl/sig11/
Well articulated but I do not know how much substatinated.

If you want a memory checker take a look at
http://reality.sgi.com/cbrady/memtest86/
but I still think it will not find any problem tho.

Hope this helps

Max

--
  Massimo Morin                                _...__..-'
mmorin at schedsys.com                          .'
 (617) 484 2999 h                          .'
 (617) 512 0203 c                        .'   Airline
                                       .'    Solutions
            .------._                 ;        Today
      .-"""`-.<')    `-._           .'
     (.--. _   `._       `'---.__.-'
      `   `;'-.-'         '-    ._     Scheduling Systems Inc.
        .--'``  '._      - '   .       Three University Office Park
         `""'-.    `---'    ,          95 Sawyer Road
 ''--..__      `\                      Waltham, 02453 Massachusetts USA
         ``''---'`\      .'            +1 (781) 893-0390 x 126
      Senior       `'. '               http://www.schedsys.com
Software  Engineer   `'.



-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).