[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
1757.0. "ACCVIO IN IMPM : DYNAMIC/STATIC MCC_STACK_SIZE...?" by TENERE::HAYES (A European Telecomet ...) Mon Nov 04 1991 09:43
Hello,
My customer has been struggling with an access violation error
on DECmcc V1.1 SSB in the Iconic Map PM.
A similar problem in note 1156, indicating a MCC_STACK_SIZE problem.
They tried a lot, and today they changed the definition of the
internal tables from DYNAMIC to STATIC , and then the Iconic Map worked
again.
The problem seems to be a STACK OVERFLOW when using DYNAMIC memory.
0) Is it good to use STATIC memory, what is the difference with
DYNAMIC memory, does this may have side-effects ?
1) What is the default size MCC_STACK_SIZE? (128 or 256 pages?)
in DECmcc V1.1 ?
in DECmcc V1.2 ?
2) Will it be possible for us to set the MCC_STACK_SIZE in version 1.2
(by a logical name or ...)?
3) If not, will this be parameter be increased in version 1.2 ?
4) Can we use the frame address method 1156.2 to find the stack size?
Using this method they found that they were using only 11 pages !
5) They also asked if it is advisable to use C register variables
for heavily used variables in order to keep those variables stored in the
computer registers ?
Best regards
Catherine HAYES
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1757.1 | Can someone help MCC_STACK_SIZE in V1.2 ???? | TAEC::HAYES | A European Telecomet ... | Fri Dec 13 1991 10:00 | 1 |
|
|
| 1757.2 | stack usage in v1.2 | TOOK::CALLANDER | MCC = My Constant Companion | Fri Jan 03 1992 09:56 | 7 |
| Form V1.2 stack sizes and their usages have been drastically
changed. These changes are due to the move to CMA and the
changes to the director model used (so that the MCC director
can run on Ultrix). Please refer to the release notes for
some information on this. More info will be forthcoming as
testing continues to characterize usage of stack size.
|