Add immediate caller info to the Error constructor (probably default arg?) #724

New issue

Open

opened 2025-03-10 19:41:02 +00:00 by jade · 6 comments

jade commented

2025-03-10 19:41:02 +00:00

Owner

I don't recall the exact way, but you can get the info: it's probably best done by a defaulted argument that constructs a source location class that gets it statically.

We have been dealing with nasty problems on HEAD where we don't have exact info as to where the errors are coming from since multiple sites share the same message. Enough of this, let's do `#[track_caller]` equivalent things. I don't recall the exact way, but you can get the info: it's probably best done by a defaulted argument that constructs a source location class that gets it statically.

jade added the

devx

Area/store

labels

2025-03-10 19:41:02 +00:00

jade added this to the Error reporting project

2025-03-10 19:41:02 +00:00

jade commented

2025-03-10 19:43:40 +00:00

Author

Owner

aha: https://en.cppreference.com/w/cpp/utility/source_location

pennae commented

2025-03-10 21:53:48 +00:00

Owner

our plan was to do both that and extend the caller info at every TRY_AWAIT that propagates an exception outward. it's not a complete stack reconstruction, but it's probably close enough?

our plan was to do both that *and* extend the caller info at every TRY_AWAIT that propagates an exception outward. it's not a complete stack reconstruction, but it's probably close enough?

lix-bot commented

2025-04-06 09:35:14 +00:00

Member

This issue was mentioned on Gerrit on the following CLs:

comment in cl/2947 ("libutil: trace unwinding through async tasks")
commit message in cl/2947 ("libutil: trace unwinding through async tasks")

This issue was mentioned on Gerrit on the following CLs: * comment in [cl/2947](https://gerrit.lix.systems/c/lix/+/2947) ("libutil: trace unwinding through async tasks") * commit message in [cl/2947](https://gerrit.lix.systems/c/lix/+/2947) ("libutil: trace unwinding through async tasks")