| Summary: | VALGRIND_CLO_CHANGE does not update vex_control | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Florian Krohm <flo2030> |
| Component: | general | Assignee: | Florian Krohm <flo2030> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | add LibVEX_set_VexControl | ||
Fixed in a2f8e48b19cb3ae6a2984354f4cadbc23cf631cb |
Created attachment 183941 [details] add LibVEX_set_VexControl VALGRIND_CLO_CHANGE("--vex-iropt-verbosity=5"); has no effect on vex_control.iropt_verbosity Attached patch adds function LibVEX_set_VexControl and calls it at the end of process_dynamic_option. The alternative would have been to expose the declaration of vex_control to libvex.h. However, until now, VEX global variables are not exposed so I chose to keep it that way.