Skip to content

[2.076] Debuginfos: Use fully qualified names#2363

Merged
kinke merged 3 commits intoldc-developers:merge-2.076from
kinke:testpdb
Oct 24, 2017
Merged

[2.076] Debuginfos: Use fully qualified names#2363
kinke merged 3 commits intoldc-developers:merge-2.076from
kinke:testpdb

Conversation

@kinke
Copy link
Member

@kinke kinke commented Oct 8, 2017

No description provided.

@kinke
Copy link
Member Author

kinke commented Oct 8, 2017

This, in combination with switching from Object (no explicit fields) to Exception in runnable/testpdb.d, gets the first assertions to work; it doesn't find any debuginfos for function test15432() though (using its .mangleof). We emit the human-readable name as DI function name and its mangle as DI function linkage name; maybe just a bug in LLVM 5, I haven't digged deeper - also because llvm-pdbutil dump -symbols testpdb.pdb crashes due to a failing assertion.

@rainers
Copy link
Contributor

rainers commented Oct 9, 2017

I use https://github.com/Microsoft/microsoft-pdb/tree/master/cvdump to dump debug information in object or PDB files.

As it seems, LDC doesn't write a S_PUB32 for the function, but only a LF_FUNC_ID with the prettyfied name. That doesn't seem to make a big difference to the debugger, though.
I'm not sure how portable that specific test15432() is anyway, as it tests for specific dmd like generated code bytes, so it could be disabled for LDC.

@kinke kinke changed the title [2.076] Debuginfo improvements [2.076] Debuginfos: Use fully qualified names Oct 22, 2017
@kinke kinke merged commit 480d3fb into ldc-developers:merge-2.076 Oct 24, 2017
@kinke kinke deleted the testpdb branch October 24, 2017 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants