jingham requested changes to this revision. jingham added a comment. This revision now requires changes to proceed.
I'm not entirely clear what problem this is solving. Any actor setting breakpoints can already choose the match depth by simply providing that many directory components. I.e. if I know I have subdir1/foo.cpp and subdir2/foo.cpp I can set a breakpoint on only one of them by doing: (lldb) break set -f subdir1/foo.cpp -l 10 So an IDE could implement this by simply passing either the base name or the base name plus one sub directory, etc. As you say, that's what command line users do anyway, they seldom type out full paths. So this is really about IDE's running lldb, and this seems more like a feature the IDE should offer, not lldb. It also seems awkward to do all this work as part of the breakpoint filtering - which as you have seen is somewhat delicate code. After all, you can implement "only match the last N components" by only submitting the last N components when looking up the files. So it would be much more straightforward to strip the leading path components from the file name when you create the breakpoint and you don't have to muck with the filtering at all. That would also help remove some confusion when you see that the path submitted was /foo/bar/baz.cpp but I matched /some/other/bar/baz.cpp (but not /some/other/different/baz.cpp) because I has set the match suffix count to 1. It would be nice to have break list show me exactly what it was going to match on. I am also not sure doing this as a general setting for values other than 0 is really helpful. So far as I can tell, you would use a value of 1 because you know that though you might have files with duplicate names they are always disambiguated by their parent directory name. Using a value of 2 says the names are disambiguated by the two parent directory names. But there's no guarantee that one value is going to work for all the files in your project and having to change a global setting from breakpoint to breakpoint is awkward. I also don't like that this makes breakpoint settings depend on the history of the session. For instance: a) Set the partial match to on and the depth to 2 b) Set a file & line breakpoint c) Change the partial match depth to 0 d) a library gets loaded with a file that wouldn't have matched with depth of 2 but does with 0 Also, you are supposed to be able to save breakpoints & restore them and provided your binaries haven't changed you will get the same breakpoints. Now, for that to work, you also have to restore some target setting that wasn't saved with the breakpoints. I wouldn't mind so much if this were passed in to the breakpoint setting directly, though again, I don't really see the point since this is mostly for IDE's and they can strip however much they want off a path before submitting it w/o involving lldb. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D129307/new/ https://reviews.llvm.org/D129307 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
