feat(test): Add DWARF_VERIFY flag on DWARF tests#13754
feat(test): Add DWARF_VERIFY flag on DWARF tests#13754RazvanN7 merged 2 commits intodlang:masterfrom
Conversation
|
Thanks for your pull request, @ljmf00! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#13754" |
|
This still requires some changes on |
4c57413 to
d2f891c
Compare
Signed-off-by: Luís Ferreira <contact@lsferreira.net>
d2f891c to
ed2fa9b
Compare
|
Why global variables are shared in FreeBSD? CI fails: |
570692d to
75a7868
Compare
Fixed. FreeBSD 11 uses an older version of llvm. Updated to LLVM 12.0. I still can't understand why global variables are always shared. |
74a133f to
aa7ad8e
Compare
DWARF readers and debuggers tend to ignore errors and try to proceed as much as possible. objdump dumping the tags, doesn't necessarily mean that the DWARF abbreviations are correct -- e.g. the reader could halt in the end, with the last abbreviation, in which the output test can't verify. Introducing a DWARF verifier is a good way to check conformancy with the standard. Signed-off-by: Luís Ferreira <contact@lsferreira.net>
aa7ad8e to
ece7ea7
Compare
Are those going to be re-enabled at some point? |
Yes. |
@RazvanN7 Perhaps this is something that could have some attention, or is it an ABI requirement? |
|
I have no clue. |
Who can we tag to clarify this? Is there any FreeBSD maintainer? I doubt the global variables are shared otherwise, some code wouldn't work as expected. Can be a DWARF issue, but I can't relate any FreeBSD specific code that does this, so I'm a bit confused. |
The other tests are disabled because of inconsistency with DWARF4/5 and
.debug_arangessection.