I think as combination of explicit symbol search path + something similar to Microsoft's symsrv would be a good "real" solution (and yes, that would be packaged as a SymbolVendor, outside SymbolFilePDB)
For short term, I don't see a clearly superior alternative to searching the current directory. On Tue, Dec 11, 2018 at 12:02 PM Pavel Labath <pa...@labath.sk> wrote: > On 11/12/2018 20:34, Zachary Turner wrote: > > I meant the location of the minidump. So if you have C:\A\B\C\foo.dmp > > which is the dump file for bar.exe which crashed on another machine, > > then it would look for C:\A\B\C\bar.pdb. That actually seems like > > fairly intuitive behavior to me, but maybe I'm in the minority :) > > > > We can see what Pavel, Adrian, and others think though or if they have > > any other suggestions. > > > > It sounds like there is a precedent for searching in CWD. I don't know > how useful it is (I traced it back to r185366, but it is not mentioned > there specifically), but it is there, and I guess it's not completely > nonsensical from the POV of a command line user. > > I guess we can just keep that there and not call it a hack (though, the > fact that the searching happens inside SymbolFilePDB *is* a hack). > > Searching in the minidump directory would also make sense somewhat, but > I expect you would need more plumbing for that to happen (and I don't > know of a precedent for that). > > pl >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
