Crash, Boom, Bang...

Question

We experienced a strange problem a couple days ago:
We shuffled our projects & supplier plans around to clean things up about
a week ago. Things ran fine, but after a week, suddenly some windows
would bomb with the following error upon doing an Open().
After playing around with it for a while, I got tired of messing with it, &
un-checked out the 2 or 3 window classes. Suddenly they worked fine!
The next day a different window began doing the same thing. On a whim,
I named all the grid fields on the window. (We usually don't name each
grid field). The problem stopped.
To make sure I un-checked out the class, & it blew up. I named the grid
fields again and it worked!
Did I fix the problem or was it just coincidence?
Sometimes I would get a system error: Trying to get the value of an
attribute from a NIL object and the array on the window was indicated.
I guess my real question is: Do ALL widgets on a window HAVE to be
named? (ie. TextGraphics, Gridfields, Frames, etc)
Thanks.
Steven Barnes
[email protected]
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation in the Forte
executable:
ftexec Version 3.0.F.2
Windows NT
Copyright (c) 1994, Forte Software, Inc.
All Rights Reserved.
Portions (c) Apple Computer Inc., (c) 1984-1990 FairCom Corporation,
(c) 1989-1993 Objectivity, Inc., (c) Servio Corporation
Wed Nov 19 22:51:33 1997
Fault at 27-Feb-1998 10:56:02, pid '4294746757', node 'BARNES':
User Name: sbarnes
Machine Name: *] *ÿÿ ÿKb with 1 CPU(s)
OS version 4.0
Loading symbols for ...
Stack backtrace ...
1000866f 1000866f (02273808,0224e6d0,00000000,00000001)
End of Stack Backtrace
=========================================================
Type Service Flags Level
err sh * 255
cfg sp 8 255
Type Service Flags Level
err sh * 255
Exception escaped from terminating task BaseWindow.StartMethod:
FATAL ERROR: System segmentation/access violation caught.
Class: qqos_SystemException
Error #: [101, 321]
Detected at: qqos_MainExFilter at 1
Last TOOL statement: method QueueCountWin.
Error Time: Fri Feb 27 10:56:02
Exception occurred (locally) on partition "VISMenuPrj_CL0_Client",
(partitionId =
34347A00-7C9C-11D1-AB28-2B7FBBC8AA77:0xa58:0x3, taskId =
[34347A00-7C9C-11D1-AB28-2B7FBBC8AA77:0xa58:0x3.38]) in
application
"FTLaunch_cl0", pid 4294746757 on node BARNES in environment
VCMDevelopmentEnv.
Warning: Unable to close 5 Window(s) after waiting for 15 seconds;
continuing with shutdown anyway.

Answer 1

I had accidentally deleted a <textgraphic> from a derived window when
the parent had the <textgraphic>. In other words. The textgraphic
belonged to the parent and it was on display in the child window. I had
strange compilation problems with that widget after that. I tried all
possible permutations to set the problem right - removed all inheritance
and set it back again, deleted the widget from the super class and
created it again, renaming the widget, etc.. Nothing worked.
Finally, I had to recreate the super and derived windows all over again.
I had exported the methods. So that saved some time.
It would be a nice idea if somebody from Forte Software could explain
the complication. I am still at a loss to figure out what could have
gone wrong !
BRAJA KISHORE CHATTARAJ,
3324, Summer Park Dr., #302,
Sacramento, CA - 95834.
Work : 916-658-1561
Home : 916-927-9325
E-mail : [email protected]
[email protected]
From: [email protected][SMTP:[email protected]]
Reply To: [email protected]
Sent: Monday, March 02, 1998 5:02 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Crash, Boom, Bang...
Steve,
Do you have inheritance level among your windows ?
If yes, it is highly recommended to name all widgets in the mother
window(s),
specially grid-fields.
Hope this helps,
Vincent Figari
On 27 Feb 1998 14:29:14 GMT "Steve Barnes" <[email protected]>
writes:
We experienced a strange problem a couple days ago:
We shuffled our projects & supplier plans around to clean things up
about
a week ago. Things ran fine, but after a week, suddenly some windows
would bomb with the following error upon doing an Open().
After playing around with it for a while, I got tired of messing with
it, &
un-checked out the 2 or 3 window classes. Suddenly they worked fine!
The next day a different window began doing the same thing. On a whim,
I named all the grid fields on the window. (We usually don't name each
grid field). The problem stopped.
To make sure I un-checked out the class, & it blew up. I named the
grid
fields again and it worked!
Did I fix the problem or was it just coincidence?
Sometimes I would get a system error: Trying to get the value of an
attribute from a NIL object and the array on the window was
indicated.
I guess my real question is: Do ALL widgets on a window HAVE to be
named? (ie. TextGraphics, Gridfields, Frames, etc)
Thanks.
Steven Barnes
[email protected]
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation in the Forte
executable:
ftexec Version 3.0.F.2
Windows NT
Copyright (c) 1994, Forte Software, Inc.
All Rights Reserved.
Portions (c) Apple Computer Inc., (c) 1984-1990 FairCom Corporation,
(c) 1989-1993 Objectivity, Inc., (c) Servio Corporation
Wed Nov 19 22:51:33 1997
Fault at 27-Feb-1998 10:56:02, pid '4294746757', node 'BARNES':
User Name: sbarnes
Machine Name: *] *&yuml;&yuml; &yuml;Kb with 1 CPU(s)
OS version 4.0
Loading symbols for ...
Stack backtrace ...
1000866f 1000866f (02273808,0224e6d0,00000000,00000001)
End of Stack Backtrace
=========================================================
Type Service Flags Level
err sh * 255
cfg sp 8 255
Type Service Flags Level
err sh * 255
Exception escaped from terminating task BaseWindow.StartMethod:
FATAL ERROR: System segmentation/access violation caught.
Class: qqos_SystemException
Error #: [101, 321]
Detected at: qqos_MainExFilter at 1
Last TOOL statement: method QueueCountWin.
Error Time: Fri Feb 27 10:56:02
Exception occurred (locally) on partition "VISMenuPrj_CL0_Client",
(partitionId =
34347A00-7C9C-11D1-AB28-2B7FBBC8AA77:0xa58:0x3, taskId =
[34347A00-7C9C-11D1-AB28-2B7FBBC8AA77:0xa58:0x3.38]) in
application
"FTLaunch_cl0", pid 4294746757 on node BARNES in environment
VCMDevelopmentEnv.
Warning: Unable to close 5 Window(s) after waiting for 15 seconds;
continuing with shutdown anyway.
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]