Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362487 - EDT runtime exceptions don't report failing EGL statement location.
Summary: EDT runtime exceptions don't report failing EGL statement location.
Status: CLOSED DUPLICATE of bug 355170
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-31 09:43 EDT by Paul Hoffman CLA
Modified: 2017-02-23 14:15 EST (History)
4 users (show)

See Also:

Attachments
Test case (277 bytes, application/octet-stream)
2011-10-31 09:43 EDT, Paul Hoffman CLA 		no flags Details
library for loading database for test program (4.21 KB, application/octet-stream)
2011-10-31 09:43 EDT, Paul Hoffman CLA 		no flags Details
View All 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 Paul Hoffman CLA 2011-10-31 09:43:03 EDT 
Created attachment 206209 [details]
Test case

RBD has build option which directs that EGL exceptions should report the program and line number of the failing EGL statement when an exception occurs.

This information is very helpful in resolving program bugs.

Is there any way to do this in EDT?

Attached example shows an exception reported without this information.   If the test case wasn't written to log each step, it would be difficult to determined which SQL statement was in error.
Comment 1 Paul Hoffman CLA 2011-10-31 09:43:34 EDT 
Created attachment 206210 [details]
library for loading database for test program
Comment 2 Paul Hoffman CLA 2011-10-31 09:46:51 EDT 
Here is exception.message returned with the exception.   The line number mentioned here is the line number of a prepared SQL statement, not the EGL program.

Syntax error: Encountered "," at line 1, column 21.: [sqlstate:42X01][sqlcode:30,000]
Comment 3 Matt Heitz CLA 2012-11-14 13:52:09 EST 

*** This bug has been marked as a duplicate of bug 355170 ***