digitalmars.D.announce - Visual D 0.3.39 released - mago now supports 64-bit debugging
- Rainer Schuetze (26/26) Oct 10 2014 Hi,
- Meta (4/4) Oct 11 2014 I'm not sure what the problem is, but with this release, when I
- Rainer Schuetze (6/10) Oct 12 2014 Hmmm, I don't get errors with that. Is it reproducible? What version of
- Meta (7/13) Oct 12 2014 me a few moments ago, but I have tried reproducing it twice
- Rainer Schuetze (4/16) Oct 13 2014 My email is r.sagitario at gmx dot de.
- FrankLike (16/16) Oct 13 2014 Sorry, Rainer,
- Rainer Schuetze (4/20) Oct 13 2014 There seems something wrong with the cv2pdb conversion.
Hi, there is a new version of Visual D available for download at http://rainers.github.io/visuald/visuald/StartPage.html It is telling that after such a long time since the last release the major feature is the update of another project that is just installed with Visual D, but I think it is pretty important: * Mago, a debugging engine that integrates into Visual Studio and is dedicated to support the D programming language, is now capable to debug Win64 applications aswell! Other highlights of this release: * added editor margin to display coverage counters and percentage (see http://rainers.github.io/visuald/visuald/Coverage.html for an example) * integration of DParser, the semantic engine that also powers Mono-D, has been updated to the latest version. * support for tab/indentation settings set by .editorconfig plugin * new "Compile & Debug" command for script-like D programs that you don't want to create a project for. The full version history can be found here: http://rainers.github.io/visuald/visuald/VersionHistory.html Visual D is a Visual Studio extension that adds D language support to VS2005-20013 and is written in D. Its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests are welcome. Best, Rainer
Oct 10 2014
I'm not sure what the problem is, but with this release, when I open a new file and select "empty D module", after a few seconds devenv.exe goes berserk and starts eating up my CPU. At that point, Visual Studio becomes unresponsive.
Oct 11 2014
On 12.10.2014 02:27, Meta wrote:I'm not sure what the problem is, but with this release, when I open a new file and select "empty D module", after a few seconds devenv.exe goes berserk and starts eating up my CPU. At that point, Visual Studio becomes unresponsive.Hmmm, I don't get errors with that. Is it reproducible? What version of VS are you using? Could you create a minidump of the frozen Visual Studio with the Pocess Explorer [1] and send it to me? Maybe I can see where it is going beserk. [1] http://technet.microsoft.com/de-de/sysinternals/bb896653.aspx
Oct 12 2014
On Sunday, 12 October 2014 at 08:17:33 UTC, Rainer Schuetze wrote:Hmmm, I don't get errors with that. Is it reproducible? What version of VS are you using?I can reproduce it by opening Visual Studio, going to File > NewFile > D > Empty D Module, and editing the file. It happened tome a few moments ago, but I have tried reproducing it twice afterward and I couldn't. It's happened multiple times, however, so it's not a fluke.Could you create a minidump of the frozen Visual Studio with the Pocess Explorer [1] and send it to me? Maybe I can see where it is going beserk.Where can I email you at? I use the web interface, so I'm unable to see the email addresses that messages come from.
Oct 12 2014
On 12.10.2014 21:37, Meta wrote:On Sunday, 12 October 2014 at 08:17:33 UTC, Rainer Schuetze wrote:My email is r.sagitario at gmx dot de. If it isn't too large, you can also attach it to a bug report here: https://issues.dlang.org/enter_bug.cgi for component "VisualD".Hmmm, I don't get errors with that. Is it reproducible? What version of VS are you using?I can reproduce it by opening Visual Studio, going to File > New > File > D > Empty D Module, and editing the file. It happened to me a few moments ago, but I have tried reproducing it twice afterward and I couldn't. It's happened multiple times, however, so it's not a fluke.Could you create a minidump of the frozen Visual Studio with the Pocess Explorer [1] and send it to me? Maybe I can see where it is going beserk.Where can I email you at? I use the web interface, so I'm unable to see the email addresses that messages come from.
Oct 13 2014
Sorry, Rainer, I find it didn't get the Debug info ! I test it by DGui. Converting debug information... "Debug\dguiTest.exe" not created! Building Debug\dguiTest.exe failed! Project Property → Compiler → Debug → Debug Info The Default item is 'Symbolic(suitable for Mago)'. But I use the vs's item : 'Symbolic(suitable for VS debug engine)' Then get the bad info: Building Debug\dguiTest.exe... Converting debug information... "Debug\dguiTest.exe" not created! Building Debug\dguiTest.exe failed! Where is my Error? Maybe it's the Visual D 's Error? Thank you,I'm waiting for your answer.
Oct 13 2014
On 13.10.2014 14:59, FrankLike wrote:Sorry, Rainer, I find it didn't get the Debug info ! I test it by DGui. Converting debug information... "Debug\dguiTest.exe" not created! Building Debug\dguiTest.exe failed! Project Property → Compiler → Debug → Debug Info The Default item is 'Symbolic(suitable for Mago)'. But I use the vs's item : 'Symbolic(suitable for VS debug engine)' Then get the bad info: Building Debug\dguiTest.exe... Converting debug information... "Debug\dguiTest.exe" not created! Building Debug\dguiTest.exe failed! Where is my Error? Maybe it's the Visual D 's Error? Thank you,I'm waiting for your answer.There seems something wrong with the cv2pdb conversion. Please open a bug report at https://issues.dlang.org/enter_bug.cgi and quote the file Debug\dguiTest.buildlog.html
Oct 13 2014
There seems something wrong with the cv2pdb conversion. Please open a bug report at https://issues.dlang.org/enter_bug.cgi and quote the file Debug\dguiTest.buildlog.htmlI test it by dfltest.exe The bug has reported on Issue 13641 .
Oct 20 2014
On Monday, 20 October 2014 at 15:33:55 UTC, FrankLike wrote:It's not a bug,VD0.3.39 is very good. I have stop the Issue 13641 ,and set it's invalid. The error's reason is my FireWall stop the mspdbsrv.exe . Thank you again.There seems something wrong with the cv2pdb conversion. Please open a bug report at https://issues.dlang.org/enter_bug.cgi and quote the file Debug\dguiTest.buildlog.htmlI test it by dfltest.exe The bug has reported on Issue 13641 .
Oct 21 2014