The functionality was disabled at https://github.com/llvm/llvm-project/commit/521c2278abb16f0148cef1bd061cadb01ef43192
- rL355402: Adds property to force enabling of GDB JIT loader for MacOS
rL355413: [lldb] Disable some of TestJITLoaderGDB.py tests on Windows
rLLDB355413: [lldb] Disable some of TestJITLoaderGDB.py tests on Windows
rLLDB355402: Adds property to force enabling of GDB JIT loader for MacOS
rGbc6b225d4292: Adds property to force enabling of GDB JIT loader for MacOS
rG05812b65db6d: [lldb] Disable some of TestJITLoaderGDB.py tests on Windows
It would be better to have the setting be an enum of "on/off/default", and then have the somebody - the current DynamicLoader plugin seems the best somebody - provide the default value if the setting hasn't been explicitly set. That way on any platform one could turn the loading on and off, which seems useful, and we wouldn't have to have a Darwin specific setting that will cease being applicable when the Darwin default switches.
That looks good. Could you add a test for this setting to the ./functionalities/jitloader_gdb/TestJITLoaderGDB.py test? I wouldn't test that the default has any particular behavior because that might change over time. But test that if you turn it on, you do get load notifications, and if you turn it off you don't. Thanks!
Do we need both this and the enable-jit-breakpoint setting? My impression was that the latter was meant to be used for disabling the gdb jit feature. Is the gdb plugin useful for anything if it does not set the breakpoint (i.e. enable = on, but enable-jit-bkpt = off). If it isn't, then could we just remove the latter?
Every time I tried to investigate that, I came to conclusion that it was just added as alternative for enable, but with intent to test plugin instantiation. Remoing in this patch. I can revert this change as needed.
This is causing a failure on the Windows Bot:
It was broken because of another change which is why you probably didn't get a notification. Please, fix this quickly or revert the change, so that we don't end up with more failures that are not sending notifications because the bot's been broken all morning.