================
@@ -804,6 +804,13 @@ def setUpCommands(cls):
)
return commands
+ def getDebugInfoSetupCommands(self):
+ if self.getDebugInfo() == "native-pdb":
----------------
DavidSpickett wrote:
As one half of Windows lldb bots, I can say that Linaro is not going to put
another builder online for this. Pretty safe to assume that @vvereschaka would
not want to either.
> Having a pdb category to get clang to produce pdb debug info makes perfect
> sense. I'm not so sure about using that category to select the plugin kind --
> particularly if the end goal is to remove the non-native plugin completely.
Given this end goal. Once we are down to one plugin, then PDB can act as a
debug info category like the others.
So in the meantime, I would be happy to do is add an extra `check-whatever` to
our Windows on Arm bot.
> When I made the suggestion to use settings I was imagining you would be
> setting it on a per-run basis via the --setting flag to dotest.py. Would that
> be an option?
We could implement this, ideally with a reduced scope `check-lldb-pdbstuff`.
Or we could use dotest.py directly? Anything that cuts down the time because
the test step is already around 25 minutes.
It's ugly but could you come up with `dotest.py -p <giant regex that covers all
the things we think we need>`?
https://github.com/llvm/llvm-project/pull/149305
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
