[Lldb-commits] [lldb] [lldb] Add support for changing char in Scalar::SetValueFromCString (PR #67784)

2023-09-29 Thread Pavel Kosov via lldb-commits
https://github.com/kpdev created https://github.com/llvm/llvm-project/pull/67784 When we trying to change not the whole string, but single character in it - lldb's ValueObject fits in Scalar and therefore lldb trying to update it as a Scalar value which is currently only support numbers, so cha

[Lldb-commits] [lldb] [lldb] Add support for changing char in Scalar::SetValueFromCString (PR #67784)

2023-09-29 Thread Pavel Kosov via lldb-commits
kpdev wrote: Depends on: https://github.com/llvm/llvm-project/pull/67309#issuecomment-1740657973 https://github.com/llvm/llvm-project/pull/67784 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/

[Lldb-commits] [lldb] [lldb] Add support for changing char in Scalar::SetValueFromCString (PR #67784)

2023-09-29 Thread via lldb-commits
jimingham wrote: This seems like a somewhat limited way to poke a character into the value if the string has more than one character already in it. If you are trying to do more fancy setting of the contents of an SBValue, then it would be more straightforward to get the SBData for the value wi

[Lldb-commits] [lldb] [lldb] Add support for changing char in Scalar::SetValueFromCString (PR #67784)

2023-10-05 Thread Pavel Kosov via lldb-commits
kpdev wrote: > This seems like a somewhat limited way to poke a character into the value if > the string has more than one character already in it. > > If you are trying to do more fancy setting of the contents of an SBValue, > then it would be more straightforward to get the SBData for the va