Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

file/line not available for unexpected exceptions #30

Closed
philsquared opened this issue Apr 20, 2011 · 5 comments
Closed

file/line not available for unexpected exceptions #30

philsquared opened this issue Apr 20, 2011 · 5 comments

Comments

@philsquared
Copy link
Collaborator

If an exception is thrown outside of one of Catch's assertion macros the file/ line info is obviously not available for the throw site.
However, the file/line of the test case itself (or the section) should be available and these should be used instead.

@philsquared
Copy link
Collaborator Author

Initial cut checked in. Still a work in progress.
Only works for TEST_CASE (not SECTIONs yet) - and file/ line still not propogated in all cases

@philsquared
Copy link
Collaborator Author

Works for sections no - unable to repro issue with exceptions outside sections not reporting file/ line

@philsquared
Copy link
Collaborator Author

Works for sections no - unable to repro issue with exceptions outside sections not reporting file/ line

@byzhang
Copy link

byzhang commented Apr 15, 2014

Hi @philsquared ,
What's the status of this issue? I'm using Catch 1.0 Build 33, and meet an exception w/o file/line telling me where is the exception thrown:

FAILED:
due to unexpected exception with message:
Invalid row access index

@philsquared
Copy link
Collaborator Author

Hi @byzhang.

I don't believe I've seen this issue (or seen it reported, before your comment here) since my last report here - 3 years ago!

Is there any more info you can provide? Perhaps a minimal, complete, example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants