diff options
| author | bors <bors@rust-lang.org> | 2019-08-28 17:49:37 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-08-28 17:49:37 +0000 |
| commit | 17e73e801a75559eac5c932ff07bd9c8499a1364 (patch) | |
| tree | d961146b748423e806c5be7aa5b7168ee41af23b /src/libstd/sys/unix/stack_overflow.rs | |
| parent | c4223726c354642705d87b9837933e3c3f38a2d8 (diff) | |
| parent | 61ff27aa1cc71042a7f3699713d38b1d1ed2b4c5 (diff) | |
| download | rust-17e73e801a75559eac5c932ff07bd9c8499a1364.tar.gz rust-17e73e801a75559eac5c932ff07bd9c8499a1364.zip | |
Auto merge of #63875 - philipc:issue-57822, r=michaelwoerister
debuginfo: give unique names to closure and generator types
Closure types have been moved to the namespace where they
are defined, and both closure and generator type names now
include the disambiguator.
This fixes an exception when lldb prints nested closures.
Fixes #57822
I haven't included the `DW_AT_artificial` changes discussed in #57822 because they make the output worse IMO, but I can easily add these if still required. For example, for the new test case the output is now:
```
(lldb) p g
(issue_57822::main::closure-1) $1 = closure-1(closure(1))
```
but adding `DW_AT_artificial` changes this to:
```
(lldb) p g
(issue_57822::main::closure-1) $0 = closure-1 {
}
```
Note that nested generators didn't cause the exception. I haven't determined why, but I think it makes sense to add the disambiguator for them too. It feels like we still don't really understand why closures were causing an error though.
r? @michaelwoerister
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
