Re: cv2pdb: cannot add symbols to module, probably msobj140.dll missing

2017-08-21 Thread Johnson via Digitalmars-d-debugger
On Monday, 21 August 2017 at 06:16:49 UTC, Rainer Schuetze wrote: On 21.08.2017 05:24, Johnson wrote: On Monday, 21 August 2017 at 03:18:38 UTC, Johnson wrote: [...] This just started happening too and a few hours ago I upgraded VS, so maybe the msobj140.dll changed and broke cv2pdb?  I

Re: cv2pdb: cannot add symbols to module, probably msobj140.dll missing

2017-08-20 Thread Johnson via Digitalmars-d-debugger
On Monday, 21 August 2017 at 03:18:38 UTC, Johnson wrote: All of a sudden I'm getting this error. All I did was comment out a huge block of code so I could check something. The code compiles but the pdb conversion gives me that error ;/ Uncommenting out the code allows it to work again. I

cv2pdb: cannot add symbols to module, probably msobj140.dll missing

2017-08-20 Thread Johnson via Digitalmars-d-debugger
All of a sudden I'm getting this error. All I did was comment out a huge block of code so I could check something. The code compiles but the pdb conversion gives me that error ;/ Uncommenting out the code allows it to work again. I can't see why the code I'm commenting out would give that

Re: Debugging Visual D using Visual D

2017-08-17 Thread Johnson via Digitalmars-d-debugger
On Wednesday, 16 August 2017 at 19:35:19 UTC, Rainer Schuetze wrote: On 16.08.2017 21:18, Johnson Jones wrote: What's strange is that with your changes, privateregistry seems to use them... but it still loads the old(I think) visualD because when I try the debug the BP's are not hit and the

Re: Debugging Visual D using Visual D

2017-08-16 Thread Johnson via Digitalmars-d-debugger
On Wednesday, 16 August 2017 at 06:58:49 UTC, Rainer Schuetze wrote: On 16.08.2017 08:32, Rainer Schuetze wrote: On 16.08.2017 04:49, Johnson wrote: VisualD.dllC:\Program Files (x86)\VisualD\Debug\VisualD.dll N/AYesSymbols loaded. C:\Program Files

Re: Debugging Visual D using Visual D

2017-08-15 Thread Johnson via Digitalmars-d-debugger
VisualD.dll C:\Program Files (x86)\VisualD\Debug\VisualD.dll N/A Yes Symbols loaded. C:\Program Files (x86)\VisualD\Debug\VisualD.pdb 229 0.45.1-rc2 12/31/1969 7:00 PM 13FB-143C* [8972] devenv.exe VisualD.dll C:\Program Files (x86)\VisualD\VisualD.dll N/A Yes Cannot find or open

Re: Visual D no bp's on x64

2017-06-19 Thread Mike B Johnson via Digitalmars-d-debugger
On Sunday, 18 June 2017 at 21:02:12 UTC, Rainer Schuetze wrote: On 18.06.2017 20:25, Mike B Johnson wrote: Didn't work ;/ All I get on the output wndow is " C:\Windows\System32\dbghelp.dll unloaded. The thread 0x1ea4 has exited with code -1 (0x). The thread 0x1390 has exited with

Re: Visual D no bp's on x64

2017-06-18 Thread Mike B Johnson via Digitalmars-d-debugger
On Sunday, 18 June 2017 at 17:43:20 UTC, Rainer Schuetze wrote: On 18.06.2017 16:50, Rainer Schuetze wrote: On 18.06.2017 16:17, Mike B Johnson wrote: So, there is some issue with x64 and visual d's debugging in visual studio. That is the only file in the project. If it works on your

Visual D no bp's on x64

2017-06-18 Thread Mike B Johnson via Digitalmars-d-debugger
in the last 20mins I did the following 1. Create a new DMD/LDC project 2. Added the code import std.stdio; import core.sys.windows.windows; import std.array, std.conv; int main(string[] argv) { wchar* pCmd = cast(wchar*)to!wstring(argv.join(" ")).ptr; STARTUPINFO si;