The target.max-children-depth setting and --depth flag would be
ignored if treating pointer as arrays, fix that by always incrementing
the current depth when printing a new child.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
+1 to a test
thanks for the fix!
lldb/source/DataFormatters/ValueObjectPrinter.cpp | ||
---|---|---|
593 | seems this is now used with m_omit_summary_depth, maybe name it consumed_summary_depth? |
lldb/source/DataFormatters/ValueObjectPrinter.cpp | ||
---|---|---|
610 | I would probably factor out: if (does_consume_ptr_depth) --curr_ptr_depth; | |
lldb/test/API/lang/cpp/frame-var-depth-and-elem-count/main.cpp | ||
15 ↗ | (On Diff #529463) | Setting a breakpoint on the return is risky because there may not be any code associated with it. Something like int puts(const char *s); puts("break here"); is safer. |
seems this is now used with m_omit_summary_depth, maybe name it consumed_summary_depth?