![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
More on Debugger PathnamesDebugger pathnames are described in detail in Using the Apex Debugger.
Fully Qualified and Relative Debugger Pathnames
Debugger pathnames are strings that explicitly reference objects:
- Fully qualified debugger pathnames contain all the information necessary to specify objects uniquely. For example:
Seat_Services.Seat_Controls.Light_On
where Seat_Services is a package, Seat_Controls is a procedure within Seat_Services, and Light_On is a function within the Seat_Services procedure.
- Relative debugger pathnames derive some naming information from the content in which they are used. For example:
When the current context is Seat_Services.Seat_Controls.1s, the relative debugger pathname refers to the same object as Seat_Services.Seat_Controls.Light_On.
When a simple name is used, the debugger searches `program-wide' for subprograms (Ada or functions (C/C++) of this name (including subprograms that correspond to task bodies and package elaboration). This search enables the user to set a breakpoint or enter any subprogram or function even if its name is not directly visible.
For Ada, entities that don't correspond to subprograms (For example, packages with no elaboration subprogram, types, variables, etc.) directly visible from the current context or that are library units are also searched for.
For C/C++, entities that don't correspond to functions directly visible from the current context are also searched for.
Specification and Body Pathnames
You can distinguish between the specification and body of a program unit by using the 'Spec or 'Body attributes. For example, the pathnames Seat_Services'Spec and Seat_Services'Body denote different declarations.
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |