Support Board
Date/Time: Sat, 22 Feb 2025 09:03:44 +0000
[Programming Help] - Visual Studio Debugging Issue
View Count: 1763
| [2018-05-26 05:35:16] |
| Andy Sureway - Posts: 93 |
|
While I am debugging with Visual Studio, it gives the following error message. SierraChart_64.pdb contains the debug information required to find the source for the module SierraChart_64.exe
Does anyone ever have the same problem before? Thanks! |
| [2018-05-26 05:38:57] |
| |
|
This does not look like an error message.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-05-26 06:06:38] |
| Andy Sureway - Posts: 93 |
|
Well, the debugging process is totally stopped by the issue. I am really puzzled on how to handle the issue. Any input? Thanks! |
| [2018-05-26 06:24:20] |
| |
|
Does it show that message in the "Output" window? It is hard for us to say what the issue is without having a comprehensive understanding of the surrounding context. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-05-26 06:34:25] |
| Andy Sureway - Posts: 93 |
|
Thanks a lot for your input. It is certainly not an issue from SierraChart. It should be from Visual Studio. Perhaps not enough packages have been installed for VS. |
| [2018-05-26 07:19:26] |
| Andy Sureway - Posts: 93 |
|
Unfortunately, I still don't have a success. Attached please find the "error" screen from VS, and the components I have installed for VS. My next trial is to add the .net environment component, to see whether it will solve the issue. |
 Screen Shot 2018-05-26 at 12.14.52 AM.png / V - Attached On 2018-05-26 07:17:33 UTC - Size: 121.34 KB - 529 views Screen Shot 2018-05-26 at 12.17.00 AM.png / V - Attached On 2018-05-26 07:17:39 UTC - Size: 586.95 KB - 688 views |
| [2018-05-26 13:30:03] |
| Andy Sureway - Posts: 93 |
|
Nope, adding more VS components does not help at all. The same issue pops out.
|
| [2020-07-25 03:51:55] |
| ondafringe - Posts: 302 |
|
Two years later... did this ever get resolved? I ask because I just had the very same thing happen to me on my first debug session: After first pass through of code, I get that same message and same screen as shown in his first attachment: "SierraChart_64.pdb not loaded" And that stops debug in its tracks; can't get around it. Can anyone shed light on this? |
| [2020-07-25 15:48:10] |
| ForgivingComputers.com - Posts: 1012 |
|
You may be seeing issues based on your installation. There is a correct sequence to installing the Visual C++ compiler and Visual Studio. Please see this post: [SOLVED] Error Building locally with Visual C++ and personal .h files |
| [2020-07-25 19:06:04] |
| ondafringe - Posts: 302 |
|
I was aware of the installation sequence issues a lot of people were having, so made certain I followed the correct install order. However, I did remember I had a trial version of VS Pro 2019 from a year ago that was still installed. So just to be certain, I uninstalled that trial version, along with VS Community, along with anything else related to VS, along with anything that had C++ next to it. Once I removed all that, I restarted my PC and went through the install process again in the correct order. And I still got that same error message: "SierraChart_64.pdb not loaded" Things weren't making any sense. Turns out, that message only appeared whenever I had a break-point set, then Stepped through to the end of the code, and then, while my cursor was positioned just to the right of the very last brace at the bottom of the code, I clicked Step through or Step over to start the code recycle again. That's when I got the error message. So the solution was this: when stepping through/over code and you get to the bottom of the app, don't try to Step back up to start the code cycle again, press F5, instead. At least that works, so far. Keeping my fingers crossed! Thanks... Date Time Of Last Edit: 2020-07-25 19:11:18
|
| [2020-07-26 10:47:48] |
| ForgivingComputers.com - Posts: 1012 |
|
That is normal behavior when debugging. While your study is compiled for debugging, SierraChart_64.exe is not, so you can't single step out of your study back into the main application. Continue is required.
|
| [2020-07-26 14:27:53] |
| Tomas.R - Posts: 9 |
|
I experienced no problem with this. Have got VS2019 installed and it did not required to be uninstalled. I just installed cmd tools directly from SC, as described in on help page, it gets intalled vc++ sdk. After I restarted SC I could attach debugger, placed breakpoint and getting stoped performing on break point, straight away with no issue.
Date Time Of Last Edit: 2020-07-26 14:30:49
|
| [2020-07-26 19:02:02] |
| ondafringe - Posts: 302 |
|
It may be "normal" or "expected" behavior, but I didn't see it in the Debug documentation. Could have saved me the better part of a day uninstalling/reinstalling software for no reason! <lol> The same thing happened when I couldn't get that Crossover Study to reverse positions, only to find out -- after spending a lot of time on it -- it won't reverse if you're using Attached Orders, which I was! Nope... not in the documentation. ;) But... like I said then, SC has provided a massive amount of documentation -- so much it will turn your brain into oatmeal -- and it was inevitable that some key information would get overlooked. That's just the nature of the beast. Anyway, it's all working now, so on with the programming! :) @Thomas: Yeah, but if you Step all the way down to the bottom of your code, and then try to Step out of your code entirely, you will probably get the same error message screen I did. |
| [2020-07-26 19:21:53] |
| Tomas.R - Posts: 9 |
|
@ondafringe Ah, you are right. However, it's expected, right? Stepping out of the study method, which we have source file for, we instruct debugger to return back somewhere inside Sierra Chart code base itself and it's not possible since we do have neither Sierra Chart's source files nor debug symbols file available to use and I doubt SC team'd provide that resources to us ;-). T. Date Time Of Last Edit: 2020-07-26 19:26:07
|
| [2020-07-26 20:00:33] |
| ForgivingComputers.com - Posts: 1012 |
|
However, it's expected, right?
Exactly. |
| [2020-07-27 00:15:07] |
| ondafringe - Posts: 302 |
|
IMO, I really don't think anyone, not even SC, "expected" the error message screen or had any idea what caused that screen to show. If they, or anyone, had, the first question would have been: "Did you try to Step Into/Over your code while your cursor was at the very bottom of your code module?" They wouldn't have just bailed out on the OP's question. That's the main reason I resurrected this message thread, to keep all this together. That way, if anyone else has this problem, and does a search on the error message, they will land here and can get it figured out. Date Time Of Last Edit: 2020-07-27 00:25:16
|
| [2020-07-27 12:52:14] |
| ForgivingComputers.com - Posts: 1012 |
|
I admit I didn't look the original poster's screen shot, nor did I pay enough attention to the specific error message. Understanding the problem, which I have seen many times, I know to expect it. Also, when a Support Request is labeled [Programming Help] it is Sierra's policy to not respond to these "unless we deem it is appropriate". (See paragraph 10: Support Board Posting Information: General Information) |
| [2021-01-28 23:38:42] |
| WHum7812 - Posts: 23 |
|
Thanks Everyone for this thread.... I too experienced the same error today and as soon as I hit F5 at the last }, it worked. Thank you very much. |
To post a message in this thread, you need to log in with your Sierra Chart account: