Station crash at OS1.6/0 when calling up graphic
- Repair corrupted display element
One particular graphic at a customer site was killing the OS every time it was called up. This problem was reproduced in the GEAG lab on roc240. The stack is attached below.
Signal caught at Mon Jul 13 10:32:40 1998
signal SIGSEGV segmentation violation
( 0)Hx000823e4 HandleSignal_Fi + 0xf0 [/opt/advant/MOD-OS/bin/modos]
( 1)Hxc01310b0 _sigreturn [/usr/lib/libc.l]
( 2)Hxc0062288 toy_pt_16_130mfObjectViewFP37_OmftIterator_pt_16_13OmfObjectView + 0xc0062289 [/opt/advant/MOD-OS/bin/modos]
Stack_Trace: error while unwinding stack
state TopState has 1 # of child states
and so on. It appears that the stack was overwritten.
A display element that was corrupt was identified. Even though the display element could not be viewed via the DYB, it was still there. Looking at some of the attributes of the Display Element convinced us it was corrupt. For example, attribute MaxWidth = 69446.3, attribute NoOfCharElse = 111114 and attribute MaxOutPutSize = string 111119. Those numbers are way too large. Here's what we did to solve the problem.
- Graphics seem to crash the OS
Insert the URL that your highlighted text will link to.
Copy the video's "embed" tag into Embedded Video below.