dtdoctor: Add support for hash-based device symbols #308
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
dtdoctor only recognized ordinal-based device symbols (
__device_dts_ord_<N>), failing to diagnose errors whenCONFIG_LLEXT_EXPORT_DEV_IDS_BY_HASHgenerates hash-based symbols (__device_dts_<HASH>).Changes
dtdoctor_sca_wrapper.py: Added regex patterns to capture hash-based symbols from gcc, ld, LLVM/clang, and LLVM/lld error messages. Used negative lookahead
(?!ord_)to distinguish from ordinal symbols.dtdoctor_analyzer.py: Extended symbol parsing to handle both formats. Node lookup now attempts ordinal match first, then falls back to hash-based lookup using the
Node.hashattribute.dtdoctor.rst: Updated to mention both symbol types.
Example
Both symbol types are now supported:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.