locked
Symbols loaded (source information stripped) RRS feed

  • Question

  • Hi all,

    I have problem, when i build my DLL project, I get .dll and .pdb

    After that I use another project and load this project. After this project is loaded, all of its functions can be executed, but I cannot enter there with debugger. When I put break point there, it is white and I get "symbols not loaded" information.

    But when I open module, after loading library, it says Symbols loaded (source information stripped).

    So I can debug it by following functions in assembly, but I would like to debug it in source code, and I dont know hwy but I can't. 

    Note: .pdb is generated with /Zi, but even if i change it to /Z7 it is still not working.

    Thanks!

    Thursday, November 24, 2016 5:29 PM

Answers

  • Fixed the problem. I was including .../Symbols/... and .../Symbols.pri/... and when i removed .../Symbols/... from debugger options, it started working.

    Thanks! :)

    • Proposed as answer by Weiwei Cai Wednesday, November 30, 2016 2:58 AM
    • Marked as answer by Vladimir Vesic Wednesday, November 30, 2016 9:53 AM
    Tuesday, November 29, 2016 3:32 PM

All replies

  • Hi Vladimir Vesic,

    >> After that I use another project and load this project. After this project is loaded, all of its functions can be executed, but I cannot enter there with debugger.

    How do you use another project load this DLL project? Do you mean add reference this project directly in one solution or reference the dlls directly?

    According to your description, I create a DLL project and build it to generate .dll and .pdb file. Then copy these files to another machine. On that machine, I create a Console application and add reference for these files. When I start debug this Console application, I Open the Modules window, the dll symbols loaded correctly.

    If you want to debug it in source code, I suggest you reference the project directly in one solution, which could let you debug into the source code.

    Best Regards,
    Weiwei


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, November 25, 2016 9:21 AM
  • Well I have project 1, in which I load my, project 2 with LoadLibraryW("libPath"); 

    I build project 1, open project 2 in Visual Studio, start project 1, I go open->file and select file from project 1 where i load library, I set brakepoint there. I attatch to process of project 1, than in project 1 which is started i trigger function that uses LoadLibrary. It hits debugger, and after library loads it says that symbols for it are loaded.

    Now, if I set brakepoint in project 1, It just cant see the symbols which it loaded...

    So your idea is to reference project 2 with project 1 somewhere? This would fix this ?

    Thanks!

    Friday, November 25, 2016 12:19 PM
  • You get 'Symbols loaded (source information stripped).' regarding your own dll?
    Do you have some entry here?


    With kind regards

    Friday, November 25, 2016 3:06 PM
  • That field is empty ...

    By the way it is working with WinDBG from time to time, in terms that I am bad with using WinDBG but I got it to work so I guess .pdb file is ok, just Visual Studio after dynamically loading it fails to load symbols too.

    Thanks!

    Tuesday, November 29, 2016 2:37 PM
  • Fixed the problem. I was including .../Symbols/... and .../Symbols.pri/... and when i removed .../Symbols/... from debugger options, it started working.

    Thanks! :)

    • Proposed as answer by Weiwei Cai Wednesday, November 30, 2016 2:58 AM
    • Marked as answer by Vladimir Vesic Wednesday, November 30, 2016 9:53 AM
    Tuesday, November 29, 2016 3:32 PM
  • Hi Vladimir Vesic,

    I'm glad that you have resolved your problem and thanks for sharing your solution here.

    Please mark your reply as answer, which is benefit to other communities who has the same issue.

    If any questions in future, please feel free to come back to create new thread.

    Best Regards,
    Weiwei


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, November 30, 2016 2:58 AM