jasonmolenda wrote: > Feels like we diverted you from your original problem though, which was the > remote taking the informative errno and changing it to some meaningless value.
It should do that though, shouldn't it? We look up the ERRNO constant we got in the GDBRemoteErrno table, sending back the constant values that the gdb RSP docs define, and if it's an errno not included in that table, we send back GDB_EUNKNOWN. https://github.com/llvm/llvm-project/pull/106950 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits