-
Notifications
You must be signed in to change notification settings - Fork 159
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
panic: could not match regexp with string #826
Comments
This is becuase c2go doesn't recognise one of the AST lines generated from clang. The regexp will need to be updated so it can be understood. If you want to have a go at fixing this, you can find an example here: #760 |
@s4kibs4mi :Did you find solution for your problem? I am also getting similar error. |
@elliotchance, I too have just experienced this issue. Maybe the regex is too strict and needs to more forgiving for other formats. Instead of updating the regex for my specific line:
Maybe we can clean this up. The issue #760 seems to build a regex from another regex. Can you point me in the direction where the tests for these are? |
@jtarchie because c2go parses the string rendered AST tree produced from clang there's a lot of edge cases, especially as clang gains more features, as the AWS output is just for debugging, it's not intended to be a porcelain format. I originally wanted to keep the regex as tight as possible to make sure the structs that represent the data don't become dirty over or out of sync over time, because it's such an easy to update a case when it's found. You can find all the test cases and node types in the ast package: https://github.com/elliotchance/c2go/tree/master/ast If it's an existing node type you can add a new test case for it, here is an example of adding a fix: #853 |
Error :
Source :
The text was updated successfully, but these errors were encountered: