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
Symbols don't seem to apply #24
Comments
Hard to say. Best would be to debug it locally... |
Tested using simple leaking test app… now I see something on call stack
My real application to test however has hundreds of PDBs… maybe that’s the issue ?
From: Милош Тошић [mailto:notifications@github.com]
Sent: Friday, November 24, 2017 1:19 PM
To: milostosic/MTuner
Cc: Shaked, Asaf; Author
Subject: Re: [milostosic/MTuner] Symbols don't seem to apply (#24)
Hard to say. Best would be to debug it locally...
I'd appreciate if you find what the cause is and report it back. Will leave the issue open for a few days
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#24 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXrSbcdjaw4w4OPJzAGleUtTf9fviFfvks5s5qY0gaJpZM4Qo2IS>.
This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.
|
I would be guessing at best without a repro case, and that's not really an engineering approach :) |
Thanks… I’ll do my best
From: Милош Тошић [mailto:notifications@github.com]
Sent: Tuesday, November 28, 2017 11:57 AM
To: milostosic/MTuner
Cc: Shaked, Asaf; Author
Subject: Re: [milostosic/MTuner] Symbols don't seem to apply (#24)
I would be guessing at best without a repro case, and that's not really an engineering approach :)
If you manage to reproduce the problem on a smaller scale I'd love to look into this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#24 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXrSbcK1_8Nr4VomEJNFGqLUc1ZKsu_zks5s69jzgaJpZM4Qo2IS>.
This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.
|
The DIA interface load symbols directly but not using the search path. The search path may be using in Dbg |
@darknesswind any suggestions regarding your comment? |
Sorry, I make a mistake, It is not the reason I fail to load the symbols. |
the convert result just like: UNC\\dev.test.net\release |
If you have time to contribute a fix it would be appreciated. I'm currently very busy with other projects. |
Are there any reason to make a UNC path? |
Reason was to handle very long path names, by prepending "\?" limit goes up substantially, if I remember correctly up to 32K characters, depending on Windows version. |
But why |
Hacky convenience, you could use the buffer passed in (_outBuff) or the return value if you don't care about long paths (when you know it's not long). |
Using latest release v4.0.7 on Win7 x64 (tried more than one PC)
I'm setting local store with path to output files from my build server
Opening previously recorded or recording new session
Call stack window is empty... Symbols don't seem to apply :/
What am I doing wrong ?
The text was updated successfully, but these errors were encountered: