[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

4727.0. "MCC V1.3 and Motif V1.1 Stack Dump" by DLOPAS::JUNIOR::AVERA () Fri Mar 19 1993 20:37

Hi ,

 We just installed V1.3 on a Vax 4500. 
	VMS 5.5-2, 
 	Motif 1.1,
 	Motif Window Manager patch (note 4624.2)

 We installed 1.3 before we upgraded to 1.1 of Motif, I am not sure 
if that is causing this problem, but FWIW i thought I would
mention it.

When we try to start up MCC we get the following stack dump:

 $ Manage/Enter/inter=decwindows

 X Toolkit Error: Unable to create tracking pixmap
 %CMA-F-EXCCOPLOS, exception raised; some information lost
 %TRACE-F-TRACEBACK, symbolic stack dump follows
 module name     routine name      line       rel PC    abs PC

                                             0004B4C4  0004B4C4
                                             0007C382  0007C382
                                             000771DC  000771DC
                                             0007A878  0007A878                            
 

 Any help would be appreciated.

Thanks,

Jim

T.R	Title	User	Personal Name	Date	Lines
4727.1		VERNA::V_GILBERT		`Thu Mar 25 1993 19:31`	64
	Jim, Sorry to not get back to you sooner, but I have been on vacation... The error in .0 has been discussed extensively in notes #275 and #352 in the CLT::GOBE_WIDGET conference. In some notes users mention that the error occurs on some types of workstations but not others (maybe because of differences in the servers?). Here is the latest word on how to fix it. ...........................beth =============================================================================== <<< CLT::DISK$CLT_LIBRARY3:[NOTES$LIBRARY]GOBE-WIDGET.NOTE;1 >>> -< Discussion of GObE widget >- ================================================================================ Note 275.19 Unable to create tracking pixmap. 19 of 19 WIDGET::KLEIN 25 lines 25-JAN-1993 13:23 -< widget initial size >- -------------------------------------------------------------------------------- I thought that there was a workaround for this discussed previously, but maybe not. My experience with this problem is that the tracking pixmap is created very early in the creation of the widget and that if the widget does not have a valid size at that time, creation of the tracking pixmap fails. The "bug" is that the tracking pixmap should probably not be created until the widget is realized, but the workaround is to give the widget an explicit initial size other than the default (100x100 pixels works). During the realization of the widget, the attachments will take effect and size the widget correctly, but the explicit XmNwidth and XmNheight resources give an initial size that is legal for the tracking pixmap creation logic. One thing you might do if you get stuck is to use the debugger to trap the CreateCallback for the widget. While in the CreateCallback, check the w->core.width and w->core.height values to make sure that they are large enough (100x100). I have found that by default, the widget is 10x10 which is not large enough for the tracking pixmap creation logic to work properly. Hope this helps. -steve- ------------------------------------------------- Now the bad news. We tried this and it did not work correctly. It crushed all the icons in the domain into a 100x100 pixel area, so we are doing some more investigation. In the meantime you could try something for us. We do not have access to a VAX 4500. Just to make sure everything else has been correctly installed, can you set the display to another system (non-4500) (set display/node=xxx/cre/perm and check that MCC comes up correctly there. Additionally, do you have MCC installed on any other system. If so, does it work ok, and can you set display to the 4500 and run that way. If possible, we may want to test any fix we come up with on your system, since we have no problem on any of our workstations. Regards, Verna
4727.2	?	DPD10::AVERA	When I die I hope I go To Texas...	`Fri Apr 02 1993 16:03`	13
	Beth, I read your memo, read the notes conf, but still don't understand how to correct the problem. Is there some command from vms that i need to do to make it work. It does not display on VXT2000, or a Vaxstation 3100. I can however get it to display on a PC using EXcursions. What gives ... Thanks, Jim
4727.3		BBOOP::SCAER	Boop-Boop-a-Doop	`Fri Apr 02 1993 20:35`	7
	As far as we know, there is nothing you can do. That information that I sent Verna and she posted was about a possible problem within the iconic map code and completely out of your control. ..............................beth
4727.4	MCC or MOtif ?	DLOPAS::JUNIOR::AVERA		`Wed Apr 07 1993 17:46`	7
	Is this a problem with Motif or MCC ? Would installing V1.2 of MCC correct the problem ? Would installing a earlier version of Motif corect the problem. Any help. Jim
4727.5	Possible workaround?	BARREL::LEMMON		`Mon Apr 26 1993 16:07`	14
	I am able to reproduce this when the iconic map can't access the mcc_resource.dat file in DECW$SYSTEM_DEFAULTS (/usr/lib/X11/app-defaults for ultrix) AND the user does not have one in DECW$USER_DEFAULTS (home directory for ultrix). Make sure you have access to the copy in the DECW$SYSTEM_DEFAULTS directory. Hopefully this workaround applies until we find out what is causing the problem. /Jim
4727.6	YES ITS FIXED !!!	DLOPAS::COWBYS::AVERA		`Mon Apr 26 1993 20:12`	18
	Jim, Thanks, that was a big help. As it turned out there is a logical called DECW$SYSTEM_DEFAULTS. This logical points to the following directories in this order. SYS$COMMON:[DECW$DEFAULTS.USER] SYS$COMMON:[DECW$DEFAULT.SYSTEM] SYS$LIBARY: Well the SYS$COMMON:[DECW$DEFAULT.USER] directory was corrupted and the system could not access it. We corrected the problem with the directory and it came up. Thanks all for your help on this very strange problem. It is fixed. JIM (Now, its Miller Time !)