Re: HELP! nested CASE statement

[l107353@cliffy.lfwc.lockheed.com (Garlington KE)]

Telson Cheung (cheung@SEDSystems.ca) wrote:
: With the debugger, we set 
:     Hpa_Group_Status.Last_Commanded_Hpa_Band := Vg_Dtypes.Band_C
:     while keeping 
:     Hpa_Group_Status.Last_Commanded_Hpa_Path uninitialed (ie. unknown)

: when stepping thru these lines of code in the debugger, instead of raising
: an Invalid_Path_Id exception, the program actually goes to 

:          when Vg_Dtypes.Path_A =>
:             Execution_Status := Hpa_C_A.Command_Execution_Status;

My guess? This is because Hpa_Group_Status.Last_Commanded_Hpa_Path is
equal to Vg_Dtypes.Path_A. Every variable has to have _some_ value; this
one just happened to be Path_A.

I'll go out on this limb a little longer. I will guess that Path_A is
probably represented as zero at the machine level. Some debuggers initialize
all unitialized varaiables to a known value (like zero). In fact, I recently
tracked down a bug in a DEC Ada application involving an unitialized
variable, where the application only worked properly while being run under
the debugger, using this handy hint.

Try having the debugger display the value of Last_Commanded_Hpa_Path just
before entering this section of code.

: Helps needed.
: Please also email response to cheung@sedsystems.ca

: Thanks


--
--------------------------------------------------------------------
Ken Garlington                  GarlingtonKE@lfwc.lockheed.com
F-22 Computer Resources         Lockheed Fort Worth Co.

If LFWC or the F-22 program has any opinions, they aren't telling me.