A happy new year to all of you out there!
In my preparations for my study exams I actually did find some time to manage a parser update so you can use Mono-D for dmd 2.062 now.
Even a week before I’ve got a nice contribution from foerdi - he created a small trace log parser that parses and displays a rough overview of performance data that is spitted out by dmd’s profiling feature after having executed a D program:
Here you see how to activate the feature.
This pad will be opened right after the program execution finished and the trace.log event has been created and filled:
This feature is still quite beta, but the most essential functionality has been established right now. Anyway, all credits go to foerdi. If he’s around in #d or #d.mono-d on freenode, please contact him for further ideas, recommendations or bugs.
Loading ...
5 Comments
System.MissingMethodException: Method not found: ‘MonoDevelop.Projects.ProjectConfiguration.get_ParentItem’.
at MonoDevelop.D.DProjectConfiguration.UpdateGlobalVersionIdentifiers (MonoDevelop.D.DProject prjOverride) [0x00000] in :0
MonoDevelop 3.0.2 FreeBSD 8.1-RELEASE amd64
Try to reinstall Mono-D. I tried to fix it.
is there a way to open an arbitrary trace.log file with your visualizer instead? eg if it’s generated from outside monod project. It’s good to have orthogonal tools. Also, bonus points if it can be opened from the command line, eg:
/Applications/MonoDevelop.app/Contents/MacOS/MonoDevelop –help
Not yet. The list with the executed functions only opens after the program was finished executing && if the profiling button is still toggled. Anyway a good idea. For having it as command line availability, I don’t really know if an addin can access it – but wait, probably it only needs a handler for all files called trace.log or so
It doesn’t work here (Ubuntu 12.10, 64 bit, MonoDevelop 3.10)
Build failed. Method not found: ‘MonoDevelop.Projects.ProjectConfiguration.get_ParentItem’.