Steve Roome wrote:
>
>
> So could we change the text (something like, but better worded than
> the following) in the FAQ, e.g. :
>
> Q: My programs occasionally die with Signal 11 ( or 10 ).
>
> A: Signal 11 errors are caused when your process has attempted to
> access memory which the operating system has not granted it access
> to.
>
> This could be caused by a number of different circumstances :
>
> a) Most likely, if you're developing it yourself it's buggy
> code. (We've all been there!)
>
> b) If it's a problem with part of the base FreeBSD system,
> it might be buggy code, but more often than not these problems
> are found long before us general FAQ readers get to use these
> bits of code.
>
> If these problems are only affecting you, it's probably bad
> hardware.
>
> In the case of a) you can use a debugger and find the point
> in the program which is attempting to access a bogus address
> and then fix it. [ you probably already know this if you're
> a programmer! ]
>
> In the case of b) You need to verify the settings on your
> motherboard. Checking for hardware you might be running slightly
> out of spec, too fast, or mismatched hardware. Often setting
> memory wait states too short will trigger random signal 11's.
> An overclocked CPU will possibly also exhibit strange or similar
> symptoms.
>
> Try running some memory testing programs, or do a make buildworld
> if you have the full source available for FreeBSD (after a few
> successful buildworlds it's probably safe to say the hardware
> is okay.).
>
> See the SIG11 FAQ (LINK) for more information.
>
> That's my idea for a rough draft anyway. I'm clearly illiterate
> though, please don't flame me for that!
>
I like it because it also give some simple, usefully ways to verify the
problem.
Jim
--
microsoft: "where do you want to go today?"
linux: "where do you want to go tomorrow?"
BSD: "are you guys coming, or what?"
S/MIME Cryptographic Signature
