Skip to content

Conversation

@bshastry
Copy link
Contributor

…on literal arguments

Fixes #10609

@chriseth
Copy link
Contributor

The change looks good, but I was not able to reproduce the bug.

@chriseth chriseth merged commit 1521e9e into develop Dec 15, 2020
@chriseth chriseth deleted the fix-10609 branch December 15, 2020 15:42
@bshastry
Copy link
Contributor Author

The change looks good, but I was not able to reproduce the bug.

I had to comment out the catch clauses in CommandLineInterface to make the exception throw on the command line.

@chriseth
Copy link
Contributor

Can you explain why this problem can happen? Especially for a non-builtin function, ilteralArguments should always be nullptr.

@bshastry
Copy link
Contributor Author

Can you explain why this problem can happen? Especially for a non-builtin function, ilteralArguments should always be nullptr.

Ah, sorry. The tests added don't correspond to the fix. As you said, I incorrectly assumed literal arguments are non null for user defined functions. Please see the new PR with the missing test case that fixes the out of bounds read.

PR #10613

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

Successfully merging this pull request may close these issues.

[AsmAnalysis] Out of bounds read in operator()(FunctionCall const& _funCall)

3 participants