Operating System - HP-UX
1829092 Members
3003 Online
109986 Solutions
New Discussion

Re: signal 11, Segmentation fault

 
Diego Pavón
Advisor

signal 11, Segmentation fault

 
5 REPLIES 5
Paula J Frazer-Campbell
Honored Contributor

Re: signal 11, Segmentation fault

 
If you can spell SysAdmin then you is one - anon
T G Manikandan
Honored Contributor

Re: signal 11, Segmentation fault

What is the value of mazdsiz and maxdsiz_64 parameters?


Thanks
Diego Pavón
Advisor

Re: signal 11, Segmentation fault

maxdsiz = 2566914048
maxdsiz-64bit = 2566914048
Diego Pavón
Advisor

Re: signal 11, Segmentation fault

All my problems was the compilation order. I linked with some libraries in this order:

IBS_CLARIFY = -L$(CLEARAPI)/libs -l:clearzpi.a -lmny4s -ltls4s -lCsup -lC -lstream


But when I changed this order for this other I solved my problems:

LIBS_CLARIFY = -L$(CLEARAPI)/libs -l:clearzpi.a -lmny4s -ltls4s -lCsup -lstd -lstream -lcl

I can't explain but now all the batch work without problems

lassehab
Advisor

Re: signal 11, Segmentation fault

Hi Diego,

You can use gdb like that:

$gdb -xdb -tui a.out

for starting a debugger using TUI ( Terminal User Interface ), so you can see a default terminal screen size of 24 by 80 chars, this termainal is divided into 2 windows, a source window at the top and a command window at the bottom.

It's very easy to see where your script go with SIGSEGV

after :

$b main
$run
a right angle bracket ( > ) points to the current location
After
$n ( For next )

And you follow a " > " where it's stop, so you can see which instruction is invalid

You can see assembler version with

$la asm

and source version with

$la src

Hope it's help

Regard
I love Java OS