Operating System - HP-UX
1835947 Members
3371 Online
110088 Solutions
New Discussion

stack growth failure (X11R6 problem)

 
Drolez
New Member

stack growth failure (X11R6 problem)

Hi !

I get the following message when trying to run DDD on SOME
of my 10.20 systems:

Pid 17608 was killed due to stack growth failure.
Possible causes: insufficient memory or swap, or stack size exceeded maxssize.
Memory fault(coredump)
The real problem is that the mem fault is not caused
by DDD itself, but by libX11.2 (X11R6).
Indeed,
- I have a 10.20 system where DDD runs fine, but on another
10.20 system, it does a core dump.
- If I get /usr/lib/X11R6/libX11.2 from the 10.20 which has a problem and put it on
the other 10.20, I also get the core dump.

On the right system libX11.2 has 1249280 bytes and
on the bad system it has 1327104 bytes.

So, the problem is with /usr/lib/X11R6/libX11.2.

Why are there so many different 10.20 releases of HPUX ?
That's not the 1st time I get problems because of
different 10.20 releases !!!! In fact I have never found
2 identical 10.20 installations (with same libraries) !!!!

Is there 'yet another patch' for that problem ?
How do I know which patches are installed on the system ?

TIA

Ludovic Drolez
2 REPLIES 2
melvyn burnard
Honored Contributor

Re: stack growth failure (X11R6 problem)

As far as the patching foers, to tell what isa on your system do:

swlist -l product |more

or print it or whatever you prefer.
You may also want to ensure that all the filesets are installed correctly.

do:

/usr/sbin/swlist -l fileset -a state | grep -e corrupt -e transient -e install

If anything comes back as in th efollowing example you have a fileset that is not installed correctly:

PHCO_13331.UX-CORE installed

Regarding the core dump, it is highly lkely there may be a patch for this, but you would need to check the two systems you have.

HTH
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Alex Glennie
Honored Contributor

Re: stack growth failure (X11R6 problem)

1. Looking at the chksum's you provided : The latest Motif patch contains the same binary version that causes your problems : PHSS_20661, however /usr/lib/X11R6/libX11.2 has been around since PHSS_17331.

Your working version comes from a very very old patch : PHSS_7745 S700_S800 10.20 X11R6 Motif 1.2 Runtime August 96 ! It maybe that intermediate patches may also be OK but I can't guarantee it, especially as there's over 20 to look at !

You could swremove the newer patch and replace it with an older working version, the above info will be of use .... or choose to investigate the problem further (see below).

ps I don't think youve got fileset corruption or a badly installed patch at this stage.

2. What is DDD ? Not DDE by any chance ? If it is you could always run the command line interface as opposed to the Gui ? Does it have problems ?

If you are using such an out of date Motif patch, what sort of state is the patching of the rest of the O/S & applications ? It maybe DDD or DDE have newer associated patches to cure this problem.

3. Search for further clues : try running a strings core ? more on the core file, check the Xservers log file : /var/dt/Xerrors (or vue), does the syslog.log contain any clues or is there any info in the users $HOME/.dt/errorlogs(o r.vue) ? compare swlist -l fileset ? grep PH from a good and a non working system, you maybe able to spot if the application has a specific patch installed on the working box which maybe worth investigating.