Bug 14577 – Add dustmite tool to VisualD

Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P1
Component
visuald
Product
D
Version
D2
Platform
x86_64
OS
Windows
Creation time
2015-05-11T23:30:00Z
Last change time
2015-08-05T21:12:55Z
Assigned to
nobody
Creator
turkeyman

Comments

Comment #0 by turkeyman — 2015-05-11T23:30:45Z
I'm often being asked to run dustmite on my whole program to try and reduce compiler bugs. It would be super-handy to have a button to kick off dustmite with the build configuration of the active project. Click-button ICE diagnosis is something we definitely need with D :)
Comment #1 by turkeyman — 2015-05-17T08:06:00Z
Yeah, getting the dustmite command line right for the active compiler/config/platform is really kinda hard. I have never managed to run it successfully in the proper context of my active config. I always manage to miss some details.
Comment #2 by r.sagitario — 2015-05-17T12:16:24Z
I'll look into it. Vladimir even added support some time back to reduce batch files used in the build: http://forum.dlang.org/thread/[email protected]#post-lql3bv:241n85:242:40digitalmars.com
Comment #3 by r.sagitario — 2015-06-06T13:08:03Z
Comment #4 by turkeyman — 2015-06-06T13:20:07Z
(In reply to Rainer Schuetze from comment #3) > Here is a first version with dustmite support: > https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.42-beta1 > > You can find some documentation at > http://rainers.github.io/visuald/visuald/DustMite.html Oh wow! I didn't actually think this was going to happen :) I'll try this out on my broken build at work on Tuesday.
Comment #5 by r.sagitario — 2015-06-16T21:16:19Z
> Oh wow! I didn't actually think this was going to happen :) > I'll try this out on my broken build at work on Tuesday. Did you have a chance to try it? I suspect that you'll often need a "Dustmite solution" instead of just a project...
Comment #6 by turkeyman — 2015-06-28T00:12:46Z
Just trying this out (sorry for the wait). So the first attempt said "failed on first build" before it really did anything. Then I made a couple of changes, and tried again, it asked to delete the previous attempt, I chose yes then it fired up dustmite which errored: D:\WinDev\dsignal.dustmite>C:\dev\D\dmd2\windows\bin\dustmite --strip-comments - -split *.bat:lines D:\WinDev\dsignal.dustmite "build.dustmite.bat | find \"Inter nal error\"" None => No Error while attempting to delete ..\dsignal.dustmite.test: Path still exists Retrying... object.Exception@DustMite\dustmite.d(243): Initial test fails ---------------- 0x00402A8A 0x00438AF6 0x00438ACB 0x004389E3 0x00429C28 0x74F586E3 in BaseThreadInitThunk 0x7774BCE9 in RtlInitializeExceptionChain 0x7774BCBC in RtlInitializeExceptionChain D:\WinDev\dsignal.dustmite>pause Press any key to continue . . . Is it only that it will search for "Internal Error"? So it can only reduce ICE's? Is that error emit the same for LDC? (my case at work is using LDC)
Comment #7 by r.sagitario — 2015-06-28T09:00:23Z
> Is it only that it will search for "Internal Error"? Maybe it isn't highlighted enough in the preliminary doc, but it says: "you can select the relevant error messsage in the Visual Studio build output window or focus the respective issue in the error list". This has a gotcha, though: "selection in the output window" is not the same as walking to the next/previous error with F8. The latter is a selection in the error list but only works if you have opened the error list window. "selection in the output window" is done by actually selecting text with click-drag or shift-caret-movements. For example, you should omit line number in this selection. > Error while attempting to delete ..\dsignal.dustmite.test: Path still exists Retrying... AFAICT this is a message from dustmite that indicates that you have some other process with open handles to the folder, e.g. the explorer.
Comment #8 by r.sagitario — 2015-08-05T21:12:55Z
released in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.42 If it doesn't work for you, please file bug reports.