[Lldb-commits] [PATCH] D62931: [lldb-server] Add setting to force 'g' packet use

Pavel Labath via lldb-commits lldb-commits at lists.llvm.org
Mon Nov 11 08:34:45 PST 2019


On 09/11/2019 21:41, Jan Kratochvil via lldb-commits wrote:
> On Sat, 09 Nov 2019 03:25:51 +0100, Jason Molenda via lldb-commits wrote:
>> I'm switching the default for at least the weekend via 60ab30ebce833c87bd4776f67cd9a82fe162ef9c / https://reviews.llvm.org/rG60ab30ebce83 so the bots aren't failing because of this, we can all look into this next week.  I think the best solution is to get lldb to fall back to p/P if g/G are not supported (which we need to talk to some targets), and disable debugserver's g/G packet support until I can debug where the bug is over there.
>>
>> I'm still concerned about some of the macos CI bots which use the installed debugservers, which will continue to have this g/G bug for a while, we'll figure all that out next week.
> 
> Linux Fedora 30 x86_64:
> d162e02cee74a3dbbfb1317fa9749f5e18610282
> 
>    File "/home/jkratoch/redhat/llvm-monorepo/lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/TestNoGPacketSupported.py", line 93, in test
>      self.assertEqual(rax, 0xffffffe03c778278)
> AssertionError: 0 != 18446743937285063288L
> 

This should be fixed with 135a493f3456.


More information about the lldb-commits mailing list