Re: Decorating exceptions with backtrace information
Niklas Hambüchen <[email protected]>
| Newsgroups | gmane.comp.lang.haskell.cafe,gmane.comp.lang.haskell.glasgow.user,gmane.comp.lang.haskell.ghc.devel |
|---|---|
| Message-ID | <[email protected]> |
On 5/8/20 7:52 PM, Henning Thielemann wrote:
> We are talking about the HasCallStack stack traces, yes?
> How is their emission addressed by extending exceptions with stack traces?
The way I understand the proposal, we may be equally talking about DWARF or profiling cost-center based stack traces.
From a debugging perspective, I guess the developer does not care so much about which implementation is used, as long as the trace points out the code path that led to the creation of the exception.
> What are "unintended exceptions"?
> What is an example of an "unintended exception"?
A recent example from my production server:
hPutBuf: resource vanished (Broken pipe)
_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.