Operating System - HP-UX
1748209 Members
2912 Online
108759 Solutions
New Discussion юеВ

Re: showing core dump error after connection of dual monitor

 
CP1
Occasional Advisor

showing core dump error after connection of dual monitor

Hello All,

 

Issue is after connecting two monitors in HPUX C8000 workstations display is coming in two monitors.

But problem is wherever two monitors are connected for one application (MOCKUP Dvise) its showing some core dumped error at the time of loading even small parts also.

 

But for other workstations its working fine like large parts here users can load.

 

This tool is required for aircraft designing which support huge graphics .

 

So is it happening due to dual monitor and what's the solution for that?

5 REPLIES 5
Dennis Handly
Acclaimed Contributor

Re: showing core dump error after connection of dual monitor

>it's showing some core dumped error at the time of loading

 

What signal are you getting?  Any error message before it aborts?

Install gdb and get a stacktrace with "bt".

CP1
Occasional Advisor

Re: showing core dump error after connection of dual monitor

>Any error message before it aborts?
This error its showing before core dumped.

Pid 4218 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
Or stack size exceeded maxssiz.
Vcvisual terminated due to Segmentation Violation (SIGSEGV) , core dumped
Dennis Handly
Acclaimed Contributor

Re: showing core dump error after connection of dual monitor

>Pid 4218 received a SIGSEGV for stack growth failure.  Or stack size exceeded maxssiz.

 

So either you are out of swap:  swapinfo -tam   # do it before you abort

Or the kernel parm maxssiz is too small.  What is the current value?

kmtune -q maxssiz -q maxssiz_64bit

 

What does this show:  file core

 

Or you have a programming error in your application.  Using gdb's bt will tell you if you have a recursive stack overflow.

CP1
Occasional Advisor

Re: showing core dump error after connection of dual monitor

bash-2.05# swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 8192 0 8192 0% 0 - 1 /dev/vg00/lvol2
reserve - 2830 -2830
memory 6301 2551 3750 40%
total 14493 5381 9112 37% - 0 -
bash-2.05# kmtune -q maxssiz -q maxssiz_64bit
Parameter Current Dyn Planned Module Version
===============================================================================
maxssiz 0x17f00000 - 0X17F00000
maxssiz_64bit 1073741824 - 1073741824

>you have a programming error in your application
Error is not associated with application.

It seems core dump error is happening for monitor thatтАЩs connected with ATI FireGL X3 connector 2 in all workstations.
Dennis Handly
Acclaimed Contributor

Re: showing core dump error after connection of dual monitor

>total 14493 5381 9112 37%

Seems to be enough free unless there was a big load difference.
 
>maxssiz 0x17f00000

At 400 Mb, this is probably too large.  So it isn't because maxssiz is too small.

>>you have a programming error in your application
>Error is not associated with application.

Ok, in the executable Vcvisual.

>It seems core dump error is happening for monitor ...

Were you able to use gdb to get a stacktrace?