Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355170 - Generated code should keep a stack of the source file name and the current line
Summary: Generated code should keep a stack of the source file name and the current line
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 362487 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-18 17:22 EDT by Matt Heitz CLA
Modified: 2017-02-23 14:16 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Heitz CLA 2011-08-18 17:22:55 EDT 
There are at least two beneficial ways we could use this information.

* We can create stack frame objects to pass to Throwable.setStackTrace(), so the exceptions we throw have a nice EGL stack trace.  That's understandable to the EGL programmer.

* When we catch a NullPointerException we should be able to tell if it came from generated code, the runtime, or an external type.  If it came from an external type, change it into a JavaObjectException instead of a NullValueException.  (Right now we assume every NullPointerException should be turned into a NullValueException.)
Comment 1 Matt Heitz CLA 2011-08-19 12:07:46 EDT 
More on the second item: to see if caught ex was thrown from a Java ET, compare its top stack frame with the top of the EGL call stack.
Comment 2 Matt Heitz CLA 2012-06-13 15:28:04 EDT 
The second item is solved by Bug 382546 - Improve detection of NullValueExceptions.
Comment 3 Matt Heitz CLA 2012-11-14 13:52:09 EST 
*** Bug 362487 has been marked as a duplicate of this bug. ***