Re: [lldb-dev] Support for Error Strings in remote protocol

True, but the error strings would be only available with lldb-server as well. Keeping a common table of error numbers seems like a good solution. On Wed, Jun 21, 2017 at 4:33 PM Jim Ingham wrote: > Because the gdb remote protocol docs explicitly state: > > The error response

Re: [lldb-dev] Support for Error Strings in remote protocol

Because the gdb remote protocol docs explicitly state: The error response returned for some packets includes a two character error number. That number is not well defined. we don't put much stock in the actual error numbers. If you can determine that you are talking to lldb-server, then we

Re: [lldb-dev] Support for Error Strings in remote protocol

What's the specific use case that you're trying to support with error messages in the protocol? My initial thought on this is that it's not really the debug server's job to generate human-readable error messages and that the debugger is better suited to do the job. Can this problem be solved by

[lldb-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)

LLVMers, The LLVM.org server which hosts SVN, GIT mirror, documentation, and the main LLVM.org website is moving to a new server on June 24th. As a result of the move commit access will be locked out beginning 09:00PDT on the 24th. We hope to have the

Re: [lldb-dev] Support for Error Strings in remote protocol

What we can't do is require the remote server to support the new protocol. lldb-server isn't the only thing we talk to, and failing because we didn't get a specific non-RSP conformant error packet would be bad. I like Pavel's idea of enabling it via a Q packet, and after being enabled it

Re: [lldb-dev] Support for Error Strings in remote protocol

+1 one from me. I like the idea a lot. Specific details below. On 21 June 2017 at 16:31, Ravitheja Addepally via lldb-dev wrote: > Hello all, >Currently the remote protocol in LLDB does not allow sending Error > Strings in response to remote packets, it only

[lldb-dev] Support for Error Strings in remote protocol

Hello all, Currently the remote protocol in LLDB does not allow sending Error Strings in response to remote packets, it only allows for "ENN" format where N is a hex integer. In our current ongoing work, we would like to have support for Sending Error Strings from lldb-server. I would like