www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.debugger - cv2pdb: cannot add symbols to module, probably msobj140.dll missing

reply Johnson <Johnson Johnson.com> writes:
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 error ;/

Deleting the code also produces the same result.

It seems to be in use with GTK and event handlers. The handlers 
are completely isolated yet are somehow causing the problem.

You won't believe this, I'm sure, but

//Dialog.addOnDestroy((Widget w) {	});

causes the error! Must be some serious bug! Uncommenting allows 
the code to build fine.

I tried restarting visual D with no luck ;/
Aug 20 2017
parent reply Johnson <Johnson Johnson.com> writes:
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 can't see 
 why the code I'm commenting out would give that error ;/

 Deleting the code also produces the same result.

 It seems to be in use with GTK and event handlers. The handlers 
 are completely isolated yet are somehow causing the problem.

 You won't believe this, I'm sure, but

 //Dialog.addOnDestroy((Widget w) {	});

 causes the error! Must be some serious bug! Uncommenting allows 
 the code to build fine.

 I tried restarting visual D with no luck ;/


This just started happening too and a few hours ago I upgraded 
VS, so maybe the msobj140.dll changed and broke cv2pdb?  I copied 
it to the cv2pdb dir so it should have no trouble finding it. 
I've also cleaned the dir. It seems it's doing it on about 
everything I change. Going to reboot to see if that helps.
Aug 20 2017
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 21.08.2017 05:24, Johnson wrote:

 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 can't see why the 
 code I'm commenting out would give that error ;/

 Deleting the code also produces the same result.

 It seems to be in use with GTK and event handlers. The handlers are 
 completely isolated yet are somehow causing the problem.

 You won't believe this, I'm sure, but

 //Dialog.addOnDestroy((Widget w) {    });

 causes the error! Must be some serious bug! Uncommenting allows the 
 code to build fine.

 I tried restarting visual D with no luck ;/


 
 This just started happening too and a few hours ago I upgraded VS, so 
 maybe the msobj140.dll changed and broke cv2pdb?  I copied it to the 
 cv2pdb dir so it should have no trouble finding it. I've also cleaned 
 the dir. It seems it's doing it on about everything I change. Going to 
 reboot to see if that helps.
 


Unfortunately, the VS2017 15.3.1 update seems to cause quite some 
trouble. Bad linker (breaks TLS), bad vcvars*.bat (change current 
directory), and this issue, too.

I guess they changed something about the (undocumented) interface to the 
respective DLLs.
Aug 20 2017
parent reply Johnson <Johnson Johnson.com> writes:
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 
 copied it to the cv2pdb dir so it should have no trouble 
 finding it. I've also cleaned the dir. It seems it's doing it 
 on about everything I change. Going to reboot to see if that 
 helps.
 


 Unfortunately, the VS2017 15.3.1 update seems to cause quite 
 some trouble. Bad linker (breaks TLS), bad vcvars*.bat (change 
 current directory), and this issue, too.

 I guess they changed something about the (undocumented) 
 interface to the respective DLLs.


;/ That sucks ;/

I guess I might just have to install VS2015, or does that have 
issues too?

Any idea what might be the best VS version that is most 
compatible with Visual D?
Aug 21 2017
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 22.08.2017 01:27, Johnson wrote:

 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 copied it to the 
 cv2pdb dir so it should have no trouble finding it. I've also cleaned 
 the dir. It seems it's doing it on about everything I change. Going 
 to reboot to see if that helps.


 Unfortunately, the VS2017 15.3.1 update seems to cause quite some 
 trouble. Bad linker (breaks TLS), bad vcvars*.bat (change current 
 directory), and this issue, too.

 I guess they changed something about the (undocumented) interface to 
 the respective DLLs.


 
 ;/ That sucks ;/
 
 I guess I might just have to install VS2015, or does that have issues too?
 
 Any idea what might be the best VS version that is most compatible with 
 Visual D?


VS2013 and VS2015 should both be fine. Building Visual D is also tested 
on Appveyor for both, too: https://ci.appveyor.com/project/rainers/visuald
Aug 21 2017
parent Johnson <Johnson Johnson.com> writes:
On Tuesday, 22 August 2017 at 05:57:20 UTC, Rainer Schuetze wrote:

 On 22.08.2017 01:27, Johnson wrote:

 On Monday, 21 August 2017 at 06:16:49 UTC, Rainer Schuetze 
 wrote:

 On 21.08.2017 05:24, Johnson wrote:

[...]


 Unfortunately, the VS2017 15.3.1 update seems to cause quite 
 some trouble. Bad linker (breaks TLS), bad vcvars*.bat 
 (change current directory), and this issue, too.

 I guess they changed something about the (undocumented) 
 interface to the respective DLLs.


 
 ;/ That sucks ;/
 
 I guess I might just have to install VS2015, or does that have 
 issues too?
 
 Any idea what might be the best VS version that is most 
 compatible with Visual D?


 VS2013 and VS2015 should both be fine. Building Visual D is 
 also tested on Appveyor for both, too: 
 https://ci.appveyor.com/project/rainers/visuald


Ok, I'll try VS2013. Maybe it will be the most stable. Hopefully 
I can run them side by side without issues.
Aug 22 2017