X

NV5 Geospatial Blog

Each month, NV5 Geospatial posts new blog content across a variety of categories. Browse our latest posts below to learn about important geospatial information or use the search bar to find a specific topic or author. Stay informed of the latest blog posts, events, and technologies by joining our email list!



From Image to Insight: How GEOINT Automation Is Changing the Speed of Decision-Making

From Image to Insight: How GEOINT Automation Is Changing the Speed of Decision-Making

4/28/2025

When every second counts, the ability to process geospatial data rapidly and accurately isn’t just helpful, it’s critical. Geospatial Intelligence (GEOINT) has always played a pivotal role in defense, security, and disaster response. But in high-tempo operations, traditional workflows are no longer fast enough. Analysts are... Read More >

Thermal Infrared Echoes: Illuminating the Last Gasp of a Dying Star

Thermal Infrared Echoes: Illuminating the Last Gasp of a Dying Star

4/24/2025

This blog was written by Eli Dwek, Emeritus, NASA Goddard Space Flight Center, Greenbelt, MD and Research Fellow, Center for Astrophysics, Harvard & Smithsonian, Cambridge, MA. It is the fifth blog in a series showcasing our IDL® Fellows program which supports passionate retired IDL users who may need support to continue their work... Read More >

A New Era of Hyperspectral Imaging with ENVI® and Wyvern’s Open Data Program

A New Era of Hyperspectral Imaging with ENVI® and Wyvern’s Open Data Program

2/25/2025

This blog was written in collaboration with Adam O’Connor from Wyvern.   As hyperspectral imaging (HSI) continues to grow in importance, access to high-quality satellite data is key to unlocking new insights in environmental monitoring, agriculture, forestry, mining, security, energy infrastructure management, and more.... Read More >

Ensure Mission Success With the Deployable Tactical Analytics Kit (DTAK)

Ensure Mission Success With the Deployable Tactical Analytics Kit (DTAK)

2/11/2025

In today’s fast-evolving world, operational success hinges on real-time geospatial intelligence and data-driven decisions. Whether it’s responding to natural disasters, securing borders, or executing military operations, having the right tools to integrate and analyze data can mean the difference between success and failure.... Read More >

How the COVID-19 Lockdown Improved Air Quality in Ecuador: A Deep Dive Using Satellite Data and ENVI® Software

How the COVID-19 Lockdown Improved Air Quality in Ecuador: A Deep Dive Using Satellite Data and ENVI® Software

1/21/2025

The COVID-19 pandemic drastically altered daily life, leading to unexpected environmental changes, particularly in air quality. Ecuador, like many other countries, experienced significant shifts in pollutant concentrations due to lockdown measures. In collaboration with Geospace Solutions and Universidad de las Fuerzas Armadas ESPE,... Read More >

1345678910Last
«May 2025»
SunMonTueWedThuFriSat
27282930123
45678910
11121314151617
18192021222324
25262728293031
1234567
14869 Rate this article:
3.0

Getting information about the last error message

Anonym

Dave Hulslander is teaching a Scientific Programming with IDL class this week, and this morning he passed along a question from a student: when a runtime error occurs, how can you programmatically get the name of the file and the line number where the error occurred?

 

For example, let's say I have the following program:

pro throw_error
   compile_opt idl2
   
   print, a ; #fail
end
	

When called, THROW_ERROR will fail at the PRINT statement because you can't print an undefined variable in IDL:

IDL> throw_error
% PRINT: Variable is undefined: A.
% Execution halted at: THROW_ERROR         4 C:\Users\mpiper\blog\posts\20130823-get-last-er
  ror-message\throw_error.pro
%                      $MAIN$   	

You can see that IDL gives you the file and line in the file where the error occurred. But how can we get this programmatically?

Unfortunately, this information isn't included in !ERROR_STATE, the system variable that contains information on the last error that occurred, and also the place where I'd expect to find this information. Luckily, there a couple ways to get it. Here's one: use HELP with the LAST_MESSAGE and OUTPUT keywords:

IDL> help, /last_message, output=err_txt
IDL> help, err_txt
ERR_TXT         STRING    = Array[3]
IDL> print, err_txt
% PRINT: Variable is undefined: A.
% Execution halted at:  THROW_ERROR         4 C:\Users\mpiper\blog\posts\20130823-get-last-error-message\throw_error.pro
%                       $MAIN$ 
      

This is a little sloppy, but you can now use string processing routines to parse the error information out of the variable err_txt.

1 comments on article "Getting information about the last error message"

Avatar image

David Fanning

Or, you could just use cgErrorMsg from the Coyote Library. :-)

Catch, theError

IF theError NE 0 THEN BEGIN

Catch, /Cancel

void = cgErrorMsg()

RETURN

ENDIF

This will print out a nicely formatted traceback message with the line number where the error occurred.

Please login or register to post comments.