<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm-project.git/lldb/test/API/tools/lldb-dap/variables/main.cpp, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/'/>
<entry>
<title>[lldb-dap] Add: show return value on step out (#106907)</title>
<updated>2025-03-02T00:21:21+00:00</updated>
<author>
<name>Da-Viper</name>
<email>57949090+Da-Viper@users.noreply.github.com</email>
</author>
<published>2025-03-02T00:21:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=8ec0d60e28f77149eef9c865515b79bc0a5e8f41'/>
<id>8ec0d60e28f77149eef9c865515b79bc0a5e8f41</id>
<content type='text'>
https://github.com/user-attachments/assets/cff48c6f-37ae-4f72-b881-3eff4178fb3c</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/user-attachments/assets/cff48c6f-37ae-4f72-b881-3eff4178fb3c</pre>
</div>
</content>
</entry>
<entry>
<title>[lldb-dap] Updating VariableDescription to use GetDescription() as a fallback. (#77026)</title>
<updated>2024-01-12T22:12:30+00:00</updated>
<author>
<name>John Harrison</name>
<email>harjohn@google.com</email>
</author>
<published>2024-01-12T22:12:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=40a361acf5ce255054c5b2e5f67a24325bfe0398'/>
<id>40a361acf5ce255054c5b2e5f67a24325bfe0398</id>
<content type='text'>
When generating a `display_value` for a variable the current approach
calls `SBValue::GetValue()` and `SBValue::GetSummary()` to generate a
`display_value` for the `SBValue`. However, there are cases where both
of these return an empty string and the fallback is to print a pointer
and type name instead (e.g. `FooBarType @ 0x00321`).

For swift types, lldb includes a langauge runtime plugin that can
generate a description of the object but this is only used with
`SBValue::GetDescription()`.

For example:
```
$ lldb swift-binary
... stop at breakpoint ...
lldb&gt; script
&gt;&gt;&gt; event = lldb.frame.GetValueForVariablePath("event")
&gt;&gt;&gt; print("Value", event.GetValue())
Value None
&gt;&gt;&gt; print("Summary", event.GetSummary())
Summary None
&gt;&gt;&gt; print("Description", event) # __str__ calls SBValue::GetDescription()
Description (main.Event) event = (name = "Greetings", time = 2024-01-04 23:38:06 UTC)
```

With this change, if GetValue and GetSummary return empty then we try
`SBValue::GetDescription()` as a fallback before using the previous
logic of printing `&lt;type&gt; @ &lt;addr&gt;`.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When generating a `display_value` for a variable the current approach
calls `SBValue::GetValue()` and `SBValue::GetSummary()` to generate a
`display_value` for the `SBValue`. However, there are cases where both
of these return an empty string and the fallback is to print a pointer
and type name instead (e.g. `FooBarType @ 0x00321`).

For swift types, lldb includes a langauge runtime plugin that can
generate a description of the object but this is only used with
`SBValue::GetDescription()`.

For example:
```
$ lldb swift-binary
... stop at breakpoint ...
lldb&gt; script
&gt;&gt;&gt; event = lldb.frame.GetValueForVariablePath("event")
&gt;&gt;&gt; print("Value", event.GetValue())
Value None
&gt;&gt;&gt; print("Summary", event.GetSummary())
Summary None
&gt;&gt;&gt; print("Description", event) # __str__ calls SBValue::GetDescription()
Description (main.Event) event = (name = "Greetings", time = 2024-01-04 23:38:06 UTC)
```

With this change, if GetValue and GetSummary return empty then we try
`SBValue::GetDescription()` as a fallback before using the previous
logic of printing `&lt;type&gt; @ &lt;addr&gt;`.</pre>
</div>
</content>
</entry>
<entry>
<title>[lldb] Rename lldb-vscode to lldb-dap (#69264)</title>
<updated>2023-10-19T16:48:54+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2023-10-19T16:48:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=01263c6c6fb495a94fe0ccbb1420bb1ec8460748'/>
<id>01263c6c6fb495a94fe0ccbb1420bb1ec8460748</id>
<content type='text'>
Rename lldb-vscode to lldb-dap. This change is largely mechanical. The
following substitutions cover the majority of the changes in this
commit:

  s/VSCODE/DAP/
  s/VSCode/DAP/
  s/vscode/dap/
  s/g_vsc/g_dap/

Discourse RFC:
https://discourse.llvm.org/t/rfc-rename-lldb-vscode-to-lldb-dap/74075/</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rename lldb-vscode to lldb-dap. This change is largely mechanical. The
following substitutions cover the majority of the changes in this
commit:

  s/VSCODE/DAP/
  s/VSCode/DAP/
  s/vscode/dap/
  s/g_vsc/g_dap/

Discourse RFC:
https://discourse.llvm.org/t/rfc-rename-lldb-vscode-to-lldb-dap/74075/</pre>
</div>
</content>
</entry>
</feed>
