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.

Sign up for GitHub

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

Jump to bottom

State new_symbolic_buffer vs new_symbolic_value #509

Closed
feliam opened this issue Sep 21, 2017 · 1 comment · Fixed by #530
Closed

State new_symbolic_buffer vs new_symbolic_value #509

feliam opened this issue Sep 21, 2017 · 1 comment · Fixed by #530
Labels
api

Comments

@feliam
Copy link
Contributor

feliam commented Sep 21, 2017

state.py: new_symbolic_buffer vs new_symbolic_value.
One uses the keyword argument name and the other label for the same thing
@feliam feliam added the api label Sep 21, 2017
@yan
Copy link
Contributor

yan commented Sep 26, 2017

This looks to be a duplicate of #147

@yan yan mentioned this issue Oct 23, 2017
Merged
@yan yan closed this as completed in #530 Oct 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Various bug fixes. trailofbits/manticore
2 participants
@yan @feliam