Conference bulova::decw_jan-89_to_nov-90

3656.0. "appl. work on 5.2 but bombs out on 5.3-2 " by ZPOVC::KUMTONG () Wed Nov 14 1990 06:57

Hi,

We have a customer wriiten DECwindows program that was developed on VMS 5.2.
The application works fine. (on a 3100 with 8MB)
The application is then ported to another machine ,on VMS 5.3-2(3100 m38, 16MB),
with all the essential files. (no source codes as the other machine has no
C compiler license) Upon running some "file section"  of the application,
the DECwindows application bombs out with the following: 
(This is highly reproducible without fail)


%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=00849818, P0
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           001599B3  001599B3
                                                           00115A24  00115A24
UI              file_selection_required         13246      00000228  0002FA5C
                                                           001447FD  001447FD
                                                           001448A7  001448A7
                                                           0011B641  0011B641
                                                           0011B907  0011B907
                                                           0015E8E2  0015E8E2
                                                           00160F7B  00160F7B
                                                           0016122E  0016122E
                                                           00161264  00161264
                                                           0016154B  0016154B
                                                           00161529  00161529
UBICHARTS       main                            10501      00000155  0002F755


Could recompiling the application on 5.3-2 alleviate the problem ?
(or is it something else I should look for)
Would be very grateful if someone could enlighten this novice at DEcwindows.
(more info can be given if required)

Thanks in advance.

\Kum-tong
CSC, ZPOVC

I know that the print widget changed incompatibly between VMS V5.2 and V5.3.
I suggest relinking on V5.3-2 to see if that solves the problem.  This
normally should not happen, but in this case it was, I am told, unavoidable.

			Steve

Steve,

I doubt it has anything to do with printing.  The print widget wasn't even
shipped with DECwindows until V5.3 (DW V2).  Previous to that, it was
an object library available internally only.

		steve