When an error is not caught, Julia shows a stack trace with the method signatures. This is informative, but sometimes the actual arguments to the functions would be very useful too. Is there a way to have them shown? Using 0.5.0.

[image] Tamas_Papp: I want embed information in the exception that can be used to isolate and debug the error, Yes, this is just a normal exception, for example a BoundsError embeds the array and what index was accessed. [image] Tamas_Papp: I want to be able to use this even if I was not…

I was reading the manual on stack traces and thought of this issue again. My understanding is that I can get the stack trace with try ... catch, eg in this MWE: using Compat # for two-argument DomainError in 0.6 bad(x) = throw(DomainError(x, "I don't like this value.")) st = tr…

An exception can store whatever state it wants and that can be retrieved by catching the exception and inspecting it. The stacktrace itself does, however, not store an instance of the exception.

What is the correct way to use the arguments of DomainError then? They are not displayed for uncaught errors, and it seems I cannot extract them either. Are you suggesting that exceptions save global state somewhere? Wouldn’t this only work when the user has control over the source of the exception…

but the thing about exceptions is that I don’t usually expect them, then I may have to rerun a long, potentially nondeterministic computation to get the information about the problem. That’d be a very nice feature for a debugger. ipython does this with %debug.

You asked if you could extract the information from the DomainError. The answer is yes, if you catch it you can extract that information. If you want to arbitrarily inspect the stack when an error got thrown, then yuyichao’s answer applies.

Just to make sure I understand: is that answer “no, you can’t, it is impossible by design”? This is the impression I got from the other thread. OTOH it should be fairly simple to do something like julia> macro print_exception(expr) quote try $expr …

What do you want to do?? The REPL IS printing the error for you by default???

Ideally, I want embed information in the exception that can be used to isolate and debug the error, I want to be able to use this even if I was not prepared for the error (eg in interactive use). Printing is fine when the conversion to text and back is sufficient, but that is not always the case …

[image] Tamas_Papp: I want to be able to use this even if I was not prepared for the error If you mean you want to access it in a similar fashion as ans for the result and NOT what your @print_exception is doing, then I think that’s a legit and potentially handy feature for the REPL.

Getting a stack trace with function argument values

General Usage

yuyichao November 23, 2016, 4:14pm 2

No. This is the job of the debugger. See my replies in Inspecting the stack

Topic		Replies	Views
Why is displaying a stack trace with values difficult Internals & Design	3	1042	November 17, 2023
Inspecting the stack General Usage question	10	1761	July 30, 2025
Is there a way to get the stacktrace from an error object? New to Julia	8	1695	December 25, 2021
Is it possible to get an exception message as a string? General Usage exception	4	4880	April 14, 2017
How to get stacktrace and line numbers after jl_exception_occurred? General Usage embedding	0	557	December 13, 2021

Getting a stack trace with function argument values

Related topics