Conference smurf::buildhelp

1369.0. "Please add Joseph_Hui to the ACLs of V32supportx and V30supportx for bsubmits. Thanks." by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Mar 28 1995 00:33

Date Of Receipt: 	27-MAR-1995 19:37:10.99
From: 	SMURF::WASTED::"joeh@locus_ode.wdec.locus.com" "27-Mar-1995 1934"
To: 	osf_prc@mudrat.zk3.dec.com
CC: 	joeh@zk3.dec.com, odeadmin@zk3.dec.com
Subj: 	Please add Joseph_Hui to the ACLs of V32supportx and V30supportx for bsubmits.  Thanks.

------- Forwarded Message

Date:    Mon, 27 Mar 95 19:28:54 -0500
From:    joeh@zk3.dec.com
To:      osf_prc@mudrat.zk3.dec.com
cc:      ootb_submit@zk3.dec.com, joeh@zk3.dec.com
Subject: Submit request: v32supportx-2-joeh


BASELEVEL: 0
USER NAME: joeh
PRINCIPAL NAME: Joseph_Hui
SUBMIT REQUEST DATE: Mon Mar 27 19:28:53 1995
SUBMIT REQUEST DEFECT NUMBER: v32supportx-2-joeh
SUBMIT REQUEST STATUS: NEW


                            Submit Request Form

                          Digital Internal Use Only

		     USEG Support Pool Submit Request Form 
			     (Form version 1.11)
	
	General Instructions: Each part of the form contains instructions
	(indented) on how to fill out that section. It is important to
	delete the instructions and substitute your text.  When a section
	is not applicable to a particular submit, enter "n/a" in response
	to that section. It is also helpful if you indent your answers to
	make the final form more readable.

	Submit requests are reviewed every Wednesday morning.  You
	will be notified of the outcome of your request following the
	review meeting.

	  ************************************************************
	  ************************************************************
	  ** Please note that the purpose of the support pool is to **
	  ** aid in generating patch files for critical problems to **
	  ** be distributed to the Customer Support Centers (CSC's) **
	  ** Submission  requests  for  any  other  purpose will be **
	  ** rejected. Also, changes made in the support pools will **
	  ** not be merged  into the current release under develop- **
	  ** ment.  A separate  submit  MUST  be made to that pool. **
 	  ************************************************************
	  ************************************************************

1) Patch or correction title (one line):

Local fix for dxcalendar crashes in V3.2

1a) srequest will automatically fill in the following question.  This should
    always be 'BL 0 of a support pool'
    What Baselevel do you wish to submit to?
BL 0 of project v32supportx

2) Justification for this submit
   (NOTE - skip to Section 3 only if you are submitting a correction to a
   problem reported in a CLD.  It is required that this section be filled
   out for all other requests).
This submit is for providing a local fix for some dxcalendar crashes
in DEC OSF/1 V3.2 (including the one reported in CLD KAOQ37602)
by changing the code optimization level from the default -O2 to -O1
in the Imakefile.  The -O1 is a viable workaround for preventing the
crashes, until there's a solution for the -O2 compiler bug, which has
been under investigation circa Gold Minor Bl5.  Ref: OSF_QAR 27394.
Please note that I did a null delta on dwc_ui_yeardisplay.c for
ensuring recompilation.

      * If this submit is being made to fix a problem which has not previously
	been reported, but which you believe is likely to become a critical 
	customer problem if not fixed, enter a S/S QAR first and then answer
	the following questions in this section.

      * If this submit is being made to fix a customer problem that has already
 
	been reported as a QAR or as a Level 3-5 IPMT (previously called SPR)
	case, and which you believe is likely to become a critical customer 
	problem if not fixed, answer the following questions in this section.

	a. How many of our customers are likely to be affected by this problem?
 
	  
	   Very few ___    Less than half ___    More than half ___    All ___

	   All customers with the following characteristic (e.g., all customers
	   who use DECnet):

	b. How often do you expect this problem to occur?

	   Rarely ___     Occasionally ___     Frequently ___      Always ___

	   Under the following general conditions (e.g., whenever the X server 
	   is started):

	c. What critical production impact will this problem have on systems 
	   that experience it? 

	d. What is the technical workaround, if any, for this problem?

3) CLD/QAR/SPR number

      CLD/QAR/SPR    Priority    Number         Component
      -----------    --------   ---------       ---------
        CLD             2       KAOQ37602       dxcalendar

4) Which support pool(s) do you wish to submit to?

   Note:  Fixes must be tested and verified for each pool before submitting
   a srequest.  You may use one submit request form for multiple pools as
   long as the problem being fixed is the same and the information for each
   pool is on that one request.  To get the unique defect number for each pool
   you are submitting your fix to, create your request in your sandbox, back
   to the next pool and issue the following command.  Issue this command for
   each pool you plan to submit to.

		srequest -f file -nofill

   where file is the request file and its pathname.


	v32supportos	[ ]	v32supportx	[x]
	v30bsupportos	[ ]	v30bsupportx	[ ]
	v30supportos	[ ]	v30supportx	[ ]
	v20bsupportos	[ ]	v20bsupportx	[ ]
	v20supportos	[ ]	v20supportx	[ ]
	v13bsupportos	[ ]	v13bsupportx	[ ]
	v13supportos	[ ]
	advfs20support	[ ]	ase11supportos  [ ]
	
   
   YOU MUST ANSWER THIS QUESTION IF YOU ARE NOT SUBMITTING TO MORE
   THAN 1 POOL.

   If you are not submitting to all versions, please explain
   why.

5) Description of Problem:

Dxcalendar crashes if year-view is selected or if the horizontal
scrollbar in day-view is moved.

	What is the problem description that you would like to have
	with this patch when it is sent to the CSCs?  Please include
	the description of the problem you are correcting, the path
	name for where the binaries will reside (e.g., /usr/bin/grep),
	the checksums (final checksums may differ from what is on your
        submit request) and any special installation instructions that
	might be needed. (List the compiled patches which go to the
	CSC).

	NOTE: If this patch just requires a kernel rebuild only, then
	enter "kernel rebuild required".  If this patch addresses a system
	panic, you must include the stack trace of the panic or other
	information which may help a customer recognize the problem, in
	the problem description.  For example:

	=======================================================================

	/usr/bin/X11/dxcalendar            (KAOQ37602)(DEC OSF/1 V3.2)
	CHECKSUM: 06397    936(v3.2)
	---------------------
	
	Patch ID: 
1180_cal_osf

	cron does not execute all jobs queued by the 'at' command. If multiple
	jobs are queued by the 'at' command not all the jobs will be executed,
	leaving them in the queue to run at a time that has already passed.
	The same problem will happen if multiple batch jobs are executed at
	the same time. This new version of cron corrects this problem.

	=======================================================================

6) Related Patches:

	Are there any other patches that have already been released which
	must be installed along with this patch to correct the problem?
None.

7) Did the checksum change:

	This section must be filled in if you change any shared library.

	If the checksum of a shared library has changed, QUICK START will
	not work. If you must rebuild a shared library as a part of your
	change, please verify the checksum via:

	odump -D lib<whatever>.so | grep ICHECKSUM

8) Compatibility impacts:
None.
	Is compatibility or interoperability with V2.0, V1.2, V1.3 or
	ULTRIX affected by this change?

9) Cross functional impacts:

	If any of the following areas are impacted by this change, please
	indicate which of the following cross functional areas are affected
  	by this submit [please have cross functional review]:

	Installation: none.
	Security: none.
	Performance: none.
	Size: none.
	Other: none.
                                                                               
10) Code Reviewer: Steve Hsueh

11a) Integration Testing:

	For each support pool to which you are submitting a patch you
	must first test your correction in a sandbox backed against the
	corresponding vxxsupportos.nightly and the vxxsupportx.nightly
	trees. Execute the following command from ./src:

	cat ../link/Logs/Version.log 

Start Run: Sat Mar 25 21:00:34 EST 1995
Start srcpool cleanup: Sat Mar 25 21:00:34 EST 1995
Finished srcpool cleanup: Sat Mar 25 21:55:03 EST 1995
Start srcpool update: Sat Mar 25 21:55:03 EST 1995
Done srcpool update: Sun Mar 26 00:08:41 EST 1995
Start snapshot_tools: Sun Mar 26 00:08:44 EST 1995
version.build: 23
version.type: P
version.variant: A
Start snapshot_os: Sun Mar 26 00:11:01 EST 1995
Done snapshot_os: Sun Mar 26 00:21:32 EST 1995
Start build: Sun Mar 26 02:19:29 EST 1995
Done build: Sun Mar 26 13:12:01 EST 1995
Start install: Sun Mar 26 13:12:06 EST 1995
Done install: Sun Mar 26 13:50:13 EST 1995
Start nightly update: Sun Mar 26 13:57:42 EST 1995
        
	Include the output in this form.

11b) Functional Testing:
Built dxcalendar in v32supportx-backed sandbox and tested dxcalendar
on a V3.2 host and a V3.0 host with V3.2 shlibs and verified the fix
solved the reported problem with no regression observed.

	Describe the testing which was done to verify that this patch
	corrects the described problem and that this patch causes no
	other regressions.

	Please include any test scripts and/or source code you used to
	qualify this patch. If you are making a kernel change, did you
	also build and boot the Realtime and SAS kernels?

12) Standards Compliance:
N/a.

	You must refer to the Standards Guidelines in the FSRC General
	Guidelines to determine if your submit impacts any Standards. 
	Bear in mind that Standards regressions are SHOW-STOPPERS.

	The FSRT General Guidelines may be found in:

        /usr/specs/release-sw/process-baselines/fsrc_guidelines.ps_v0.2

13) Changed files:

	List of files to be "submitted" (full pathnames from the src
	directory in the ODE tree, ODE revision number, and ODE set
	name, e.g. sue_ag), use bstat -all for the list of files and the revs:

[ ./motif/clients/calendar/Imakefile ]
version 1.1.11.2 selected

[ ./motif/clients/calendar/dwc_ui_yeardisplay.c ]
version 1.1.9.2 selected

14) Inventory impact:
None.

	This section is required in order to provide an inventory of files
	that have been changed, added, or removed.  Please grep the the
	following files to find the pathname for the changed or defunct
	files.

	(Examples of master inventory subset names:)
	Base System:      
		/usr/sde/osf1/build/{submit_tree}/src/isl/data/OSF200.mi
	Workstation:      
		/usr/sde/osf1/build/{submit_tree}/src/isl/data/OSFX200.mi


	List inventory changes that will impact the output area and
	their associated subsets.

	NEW inventory files:
	CHANGED inventory files:
	DEFUNCT inventory files:

15)	Code Diffs:

	Please supply pointers to changed files. If the differences are
	less than 100 lines per file, also include the differences as
	produced by the command:

		bdiff -r$NEW -all >& bdiff.log

[ ./motif/clients/calendar/Imakefile ]
===================================================================
RCS file: ./motif/clients/calendar/Imakefile,v
retrieving revision 1.1.6.4
*** 1.1.6.4	1994/04/25 22:23:46
--- ./.rcstemp006080/Imakefile	1995/03/27 23:42:54
***************
*** 152,157 ****
--- 152,158 ----
  #else
  MEMEX_UI_OBJS = /* nothing */
  #endif
+ CDEBUGFLAGS = -O1 -Olimit 2000
  UI_OBJS = dwc_ui_calendar.o dwc_ui_alarms.o \
  	  dwc_ui_catchall.o dwc_ui_clipboard.o dwc_ui_customize.o \
  	  dwc_ui_dateformat.o dwc_ui_datefunctions.o dwc_ui_day.o \
diff -c -r1.1.6.4 ./.rcstemp006080/Imakefile

[ ./motif/clients/calendar/dwc_ui_yeardisplay.c ]
===================================================================
RCS file: ./motif/clients/calendar/dwc_ui_yeardisplay.c,v
retrieving revision 1.1.4.3
diff -c -r1.1.4.3 ./.rcstemp007269/dwc_ui_yeardisplay.c

	==================================================================
                          Digital Internal Use Only


------- End of Forwarded Message