The ABL provides a variety of logging features that will show calls (RUN statement executions, TRIGGER executions, FUNCTION calls, METHOD calls, Creation and Deletion of objects in memory, Events that are fired, etc.), however none are specific to the line of code that is executing when an error is shown or a message is produced from an ABL application.
To this end, in 9.1D01 the -debugalert parameter was introduced to the product. The below section discusses the -debugalert parameter and how to use it in various situations for finding the exact line of code where an error or message was shown.
Is it possible to find out which procedure (*.p file) generated an error message? ABL Debugging: -debugalert Startup Parameter How to identify the line number in a program as reported by 4gltrace Can the Client Session Debug Alert (-debugalert) startup parameter be used with a Run-time Client? How to log the line number of code that raises an error when using structured error handling 
