jingham added a comment.

Is there ever a reason other than performance why you would want NOT to consult 
both the Compile Unit name and also look for DW_AT_decl_file is performance?  
That doesn't seem clear to me.

If the only worry is performance, and except for that you would really always 
want the full search, then I don't see what we gain by adding --compile-unit as 
distinct from --file.  We should use target.inline-breakpoint-strategy to allow 
people to turn on or off the searching for DW_AT_decl_file for folks whose 
projects are complicated enough AND who aren't doing a lot of inlining.  "break 
set" is already over-stuffed, I don't want to add to it unless we get a 
positive benefit.

On a side note, I really wish I had made "break set" be a multi-word command, 
so you could specify the main search criteria, and then the qualifiers could be 
used more flexibly and be better documented and and you wouldn't see options 
that weren't relevant.  Like:

break set name
break set source
break set address

That wouldn't make the command any harder to type, it would even be easier 
since:

break set name foo

would shorten to:

br s n foo

instead of

br s -n foo

I wonder if it is too late to make this change?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D74136/new/

https://reviews.llvm.org/D74136



_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to