Skip to content
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

[CodeView] MSVC debugger cannot find global llvm::outs() when self-hosted #34869

Closed
llvmbot opened this issue Dec 4, 2017 · 8 comments
Closed
Labels
bugzilla Issues migrated from bugzilla debuginfo

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Dec 4, 2017

Bugzilla Link 35521
Resolution FIXED
Resolved on Jun 29, 2018 15:28
Version trunk
OS Windows NT
Blocks #28528
Reporter LLVM Bugzilla Contributor
CC @amccarth-google,@dpxf,@zmodem,@nico,@rnk

Extended Description

  1. Build LLVM using CMAKE_BUILD_TYPE=Debug using clang-cl and MSVC linker
  2. Debug any LLVM tool and set a breakpoint in main. I used llvm-pdbutil, but it doesn't really matter what you use.
  3. In the watch window, type llvm::outs().flush(). You'll see this in the result column: "identifier llvm::outs() is undefined".

Note this works when not self-hosted, and also this is a /O0 build.

@rnk
Copy link
Collaborator

rnk commented Dec 20, 2017

outs-watch-window.png
Works for me in VS.

@rnk
Copy link
Collaborator

rnk commented Dec 21, 2017

My test was x64, I still need to try 32-bit.

@rnk
Copy link
Collaborator

rnk commented Dec 21, 2017

I tried 32-bit, and it works there as well... Are you sure you weren't using LLD maybe? I can try that.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Dec 21, 2017

Definitely wasn't using LLD. Weird, maybe it had to do with the exact line of code I was calling it from. I'll have to test this again when I'm back

@nico
Copy link
Contributor

nico commented May 17, 2018

Should we wontfix this?

@llvmbot
Copy link
Collaborator Author

llvmbot commented May 17, 2018

I will attempt to reproduce this and report back.

@nico
Copy link
Contributor

nico commented May 29, 2018

Any luck reproducing?

@llvmbot
Copy link
Collaborator Author

llvmbot commented Jun 29, 2018

I'm pretty sure this was actually the same as llvm/llvm-bugzilla-archive#37634 .

Took me an entire week but I did manage to track it down and it's fixed in https://reviews.llvm.org/rL336024.

I'm marking this fixed for now

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla debuginfo
Projects
None yet
Development

No branches or pull requests

3 participants