[Bug 27205] New: TestThreadStates: StringExtractorGDBRemote.cpp packet validation failure

Subprojects LLDB
1

Bug ID 27205
Summary TestThreadStates: StringExtractorGDBRemote.cpp packet validation failure
Product lldb
Version unspecified
Hardware PC
OS All
Status NEW
Severity normal
Priority P
Component All Bugs
Assignee lldb-dev@lists.llvm.org
Reporter todd.fiala@gmail.com
CC llvm-bugs@lists.llvm.org
Classification Unclassified

I'm seeing this occasionally on the OS X LLDB CI:

Assertion failed: (!"Packet validatation failed, check why this is happening"),
function OKErrorNotSupportedResponseValidator, file
/Users/buildslave/jenkins/sharedspace/lldb@2/lldb/source/Utility/StringExtractorGDBRemote.cpp,
line 408.

[TestThreadStates.py FAILED]

leading to an exceptional exit.

The CI runs with the local Xcode's Apple-signed debugserver, not the
debugserver source in the LLDB tree.  This shouldn't matter, but I'm calling it
out in case it does.

Seems a little extreme that we're asserting on gdb packet handling?  In any
event, we need to track this down since it is starting to happen with some
regularity.
2

Todd Fiala changed bug 27205

What | Removed | Added |

Comment # 1 on bug 27205 from Todd Fiala

Assigning over to Greg.  He recently tweaked this code, and it is related to a
change in debugserver.

This might either require a new debugserver (in which case the CI has to run on
a bot with all the lldb_codesign magic set, which is something we're trying to
avoid over at LLVM.org due to build machine pooling interests), or an
adjustment for what is considered okay with older debugservers.  Either way, we
have something to investigate.