| Summary: | Ignore DW_OP_APPLE_uninit | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Nicholas Nethercote <njn> |
| Component: | general | Assignee: | Rhys Kidd <rhyskidd> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | pjfloyd, rhyskidd, tromey |
| Priority: | NOR | ||
| Version First Reported In: | 3.5 SVN | ||
| Target Milestone: | blocking3.5.1 | ||
| Platform: | Unlisted Binaries | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Nicholas Nethercote
2009-08-16 06:32:18 UTC
In order to ignore it we will need to know what it actually is - what arguments it takes and how they relate to the result it returns... (In reply to comment #1) > In order to ignore it we will need to know what it actually is - what > arguments it takes and how they relate to the result it returns... It is probably just a renaming of DW_OP_GNU_uninit (also 0xf0...). It doesn't take any arguments. It should always appear at the end of the expression, somewhat (but not completely) like DW_OP_piece. See: http://gcc.gnu.org/ml/gcc-patches/2007-06/msg00040.html I haven't seen errors for this DW_OP. Either it has been fixed or it just went away due to Apple changes to their LLVM. regtest now filters out all DW_OP warnings. |