Skip to content

[llvm][Docs] Add release note about LLDB core file improvements #123062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 16, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions llvm/docs/ReleaseNotes.md
Original file line number Diff line number Diff line change
Expand Up @@ -459,6 +459,25 @@ Changes to LLDB

* [New Core File API](https://lldb.llvm.org/python_api/lldb.SBSaveCoreOptions.html). This gives greater control on the data captured into the core file, relative to the existing `process save-core` styles.

* When opening ELF core files, LLDB will print additional information about the
signal that killed the process and the disassembly view will display actual
(relocated) targets of the jump instructions instead of raw offsets encoded in
the instruction. This matches existing behavior for live processes.

Old:
```
* thread #1: tid = 329384, 0x0000000000401262, name = 'a.out', stop reason = signal SIGSEGV

0x7f1e3193e0a7 <+23>: ja 0xfe100 ; <+112>
```

New:
```
* thread #1: tid = 329384, 0x0000000000401262, name = 'a.out', stop reason = SIGSEGV: address not mapped to object (fault address: 0x0)

0x7f1e3193e0a7 <+23>: ja 0x7f1e3193e100 ; <+112>
```

* `lldb-server` now listens to a single port for gdbserver connections and provides
that port to the connection handler processes. This means that only 2 ports need
to be opened in the firewall (one for the `lldb-server` platform, one for gdbserver connections).
Expand Down
Loading