Back to Questions
1.7k
views7
comments
Tooling issues with F# in VS 2010 Beta 1.
f#

I have been trying to profile an F# solution in the "Performance Explorer" of VS 2010, but every time I attempt to run it with Instrumentation (not CPU sampling), my program fails with access violation. In one of the programs I tried to profile, access violation was in a function that was supposed to be never called at all !

So the question is if the profiler is supposed to work or is it not yet implemented in this beta? (I can be missing something as this was my first attempt to use the VS profiler)

Edit: Checked performance report from the memory profiler (CPU sampling method), absolutely useless. Not even a single function or module name from my code. Here is a sample line:

Name Inclusive Allocations Exclusive Allocations Inclusive Bytes Exclusive Bytes

{4A0174CA-904C-F4DA-A745-0383CA74014A} 162,306 36,032 15,718,724 938,500

.

As Visual Studio 2010 Beta 1 memory profiler does not work for F# at all, are there any other options for memory profiling of F# applications? Did anybody use/used memory profiler in VS 2008? (I've uninstalled my so if it works, I would reinstall).

Thanks.

By on 5/25/2009 6:42 PM ()

I just ran the VS profiler, with allocation and lifetime options on, against a trivial F# program and it worked. I've used it before too...

By on 5/25/2009 7:15 PM ()

Thanks for your reply.

I just reinstalled Windows 7 RC instead of Vista and now memory profiler with CPU sampling as data collection worked.

Still, every time I'm launching

Analyze->Performance Wizard

while working on a project, the list of projects available for profiling is empty and I cannot add one. Have to browse for an executable. In addition, if the Data Collection method in the "Performance Wizard" is chosen "Instrumentation", the profiler fails every time with access violation.

Finally, and I don't know if all of these tooling issues are related to F#, as I don't use VS for anything else, trying to use Debug History, aka Historical Debugger, gives the error "Historical Debugging is not supported for non x86 architectures. Please adjust your platform accordingly". I ran a search, but could not find people with similar problems with C#.

I'm using Windows 7 RC on Core 2 Duo T61 laptop.

By on 5/25/2009 8:20 PM ()

Regarding platform x86, you can adjust this for F# by right-clicking the project, selecting 'Properties', going to the 'Build' tab, and changing the 'Platform target' to x86. (Or you can edit the project file (.fsproj) to include

x86

if you like working with msbuild directly.) C# and VB changed their templates in VS2010 to default to x86 (rather than AnyCPU), which explains why you might not see this there.

By on 5/25/2009 9:14 PM ()

Since you're so quick installing an RC operating system, are you by any chance using a virtual machine? I've had some strange behavior profiling in a VM as well. VS 2008 even refuses to do CPU sampling on a virtual machine, for example. (this is for C# projects, haven't tried profiling F# apps yet)

By on 5/25/2009 11:00 PM ()

CPU Sample profiling on a VM is added in VS 2010; it is not available in VS 2009.

By on 6/10/2009 9:51 PM ()

No, it's a normal, not a Virtual Machine installation.

By on 5/26/2009 12:10 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper