Bugzilla – Full Text Bug Listing
| Summary: | Sometimes get "line: not available" for records (shouldn't even be stepping into it) | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Justin Spadea <jspadea> |
| Component: | EDT | Assignee: | Justin Spadea <jspadea> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Fixed EGLJavaThread.java and EGLClassTemplate.java in java.templates. We now force a stepInto on generated lines that don't correspond to EGL source. Verified |
To reproduce, step into on: rec myrec{}; It will actually step into the record. We should only step into the record when there were initializers on one or more fields, and it should only step-end on the initializer statements. Example methods in generated records that don't map to the EGL code: Constructor ezeInitialize (when user didn't code any initializer statements) ezeSetEmpty etc...there's a lot of these methods Need to figure out how to filter these methods - idea: If there's SMAP data, and it's an EGL stratum, see if the frame's function was included in the SMAP functions. If it is, then it's a user-coded function and should not be filtered, otherwise it must be some internal function that was generated in support of the runtime and should be filtered. This solution will apply to all generated classes, not just records.