Re: [bgl-discuss] stderr signal interpretation.

[Kazutomo Yoshii <kazutomo@xxxxxxxxxxx>]

It happens when you try to dereference an illegal memory location.
As Kamil say, it's segmentation fault.

For example, you can get "signal 11" by a program like below

int main() { *( (char*)0xb0000000L )=0; return 0; }

The BG/L system generates a core file (i.e. core.0) which may give
you some idea.

$ head core.0
...
"dereferencing memory at..........0xb0000000"
...

Kamil Iskra wrote:

>On Wed, Nov 23, 2005 at 22:06:05 -0500, Jeffrey L. Tilson wrote:
>
>  
>
>>Perhaps I missed it but, where can I find the meaning of errors returned
>>by the job. For example, without much fanfare my 
>>fairly small job (c=32) return the following in stderr.
>>
>>"killed with signal 11" 
>>    
>>
>
>Aren't these simply standard UNIX signals?  For BGL, they are defined in:
>
>/bgl/BlueLight/ppcfloor/blrts-gnu/powerpc-bgl-blrts-gnu/sys-include/bits/signum.h
>
>11 would then be segmentation violation.
>
>  
>


-- 
Kazutomo Yoshii   http://www-unix.mcs.anl.gov/~kazutomo/

- --------------------------------------------------------------------
To add or remove yourself from this mailing list, use the 'notifyme'
command on any BGL machine. To remove: notifyme -n, to add: notifyme -y.