Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Categories

In this Discussion

Tags in this Discussion

Nsight 2.1 RC2 not working?
  • Vote Up2Vote Down Vogi
    Posts: 27
    Hi!

    I have now installed the CUDA 4.1 RC2, Nsight 2.1 RC2 and the 285.86-driver on my machines (Win7 Prof. 64-bit, VS2010 Ultimate, GTX480 + a second Nvidia-card (GT520 on the one and a Geforce7xxx on the other one)).

    I did the same setup and configurations as I had before with CUDA 4.0 and Nsight 2.0 and the old driver (I guess it was 280.xx). Unfortunately, when starting the debugger, now Nsight does not hit any breakpoint anymore. VS just shows the "No source correspondence". :(

    I found this in the User Guide:
    If a breakpoint cannot be resolved in a loaded module, the breakpoint will display a warning icon during the debug session. This occurs if the debugger is unable to find the source location of the breakpoint. Make sure you are using the CUDA toolkit that ships with the Parallel Nsight tools. If you are writing code based on the CUDA driver API, you can check to see if the symbol files are being generated (.cubin.elf.o files located alongside your .cubin files). Code that is based on the CUDART API does not create .cubin.elf.o files.

    Well, I am using the driver API and compile to PTX. All I can find in the output-directoy are files like "tmpxft_000013d0_00000000-11_RaytracingKernel.cpp3.o" with 0KB.

    The command-line I use for compiling is:
    "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v4.1\bin\nvcc.exe" -G0 -ptx --cl-version 2010 -ccbin "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC" -I "[path to my includes]" -I "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include" -L "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\lib" -m 64 -arch sm_20 -Xptxas -v myKernel.cu


    For more information, the PTX starts with the following:
    //
    // Generated by NVIDIA NVVM Compiler
    // Compiler built on Sat Nov 19 07:29:21 2011 (1321684161)
    // Cuda compilation tools, release 4.1, V0.2.1221
    //

    .version 3.0
    .target sm_20, debug
    .address_size 64


    So, what am I doing wrong here?
    Do I need any additional setup to Nsight 2.0?

    Thanks for your help!

    Greetings,
    Vogi
  • 12 Comments sorted by
  • Vote Up0Vote Down Jeff Davis
    Posts: 131 Accepted Answer
    Hi Vogi,

    Do I understand correctly that your setup is:

    Machine 1
    -Win7 64-bit, VS2010 Ultimate
    -GTX480
    -GT520
    -285.86

    Machine 2
    -Win7 64-bit, VS2010 Ultimate
    -GTX480
    -GeForce 7xxx series
    -285.86

    Which machine are you using as the monitor target?

    Thanks!

    -Jeff
  • Vote Up0Vote Down Vogi
    Posts: 27
    Hi Jeff!

    Yes, that's my setup.
    I use headless debugging on both machines. The CUDA and DX10 context are created always on the GTX480, and the other card (GT520 and the Geforce7) is just used for displaying the desktop, so, I start the monitor on each machine individually. I do not work on both machines at the same time, they are at different places.

    On each machine, both adapters are turned on in the Nv-System Panel and have a monitor attached to them. Aero is off. TDR is turned off of course as well as WPF hardware-acceleration.

    When I start Nsight-debugging the monitor connects to the debugger, but does not stop at the break points, which show, as said above, the "No source..." message.

    Please note however, I have an C#-Project in VS2010! It was no problem at all with Nsight 2.0, but maybe this might cause problems with Nsight 2.1 RC2?

    Furthermore, could it be that it has something to do with the new Nsight-Option Analysis/Symbol Management/Resolve Symbols? But then, this is an option under the Analysis section...

    Maybe compiling to PTX is a problem? When compiling to PTX, does it really need a second file (this ".o"-file I read about in the docs)?
    One thing I noticed is that the PTX-file compiled with G0 is 1.938KB in size, and without the G0 switch it is 4.684KB!! In case without the G0 this is MUCH more than with CUDA 4.0 btw.!

    Really hope you can help me get it working!

    Thanks a lot!

    Greetings,
    Vogi
  • Vote Up0Vote Down Jeff Davis
    Posts: 131 Accepted Answer
    Hi Vogi,

    Any chance you could pull the GeForce 7xxx and replace it with another card, at least temporarily? I have a sneaking suspicion from previous tests I've performed that it may cause sporadic issues.

    As for CUDA and C#, there should be no issue. I'll look into it though.

    Thanks!

    -Jeff
  • Vote Up0Vote Down Vogi
    Posts: 27
    Hi Jeff!

    Hmmm... maybe I could try a GTX295.
    But anyhow... I have the GT520 in the other PC and it's the same there. So I guess it would be quite a coincidence if exactly those two cards, the Geforce 7 and the GT520, would make problems?

    As I already said, there had been NO problems running Nsight 2.0 + CUDA 4.0 + 280-version-driver on this setup!
    Nsight 2.0 worked "fine" (at least it did stop at breakpoints).

    So that's why I would assume a software-error (in Nsight 2.1 RC2, CUDA4.1 RC2 or the 285er driver) or a misconfiguration on my PCs due to the installation of the new Tools (again... Nsight 2.1RC2, CUDA 4.1RC2, 285-driver).

    To reproduce my case:
    Install Win 7 Prof. 64-bit on a machine. Install VS2010 SP1 Ultimate. Install driver version 280. Install CUDA 4.0. Install Nsight 2.0.
    Configure headless debugging for Nsight (WPF acceleration, TDR, Device-configuration in nv-control-panel, Project-Options, etc...). Nsight should work and stop at breakpoints.

    Then, uninstall CUDA 4.0 and Nsight 2.0.
    Install new driver 285. Install CUDA 4.1 RC2. Install Nsight 2.1 RC2.
    Nsight does not work, i.e. does not stop at breakpoints.

    Thanks for your help!

    Greetings,
    Vogi
  • Vote Up0Vote Down Jeff Davis
    Posts: 131
    Hi Vogi,

    So that I am clear, you are seeing the issue on both machines? When installing the 285.86 driver, did you do a clean install?

    Thanks!

    -Jeff
  • Vote Up0Vote Down Vogi
    Posts: 27
    Hi Jeff!

    Yes and Yes.

    In the meantime I installed Nsight 2.1 (release) and 286.19, but behavior is exactly the same.
    Help on this issue highly appreciated!

    Thanks!

    Greetings,
    Vogi
  • Vote Up0Vote Down Jeff Davis
    Posts: 131
    Hi Vogi,

    Is this a different issue from your C# issue?

    Thanks!

    -Jeff
  • Vote Up0Vote Down Vogi
    Posts: 27
    Hi Jeff!

    Thanks for asking but, no, thats the same issue. It's just an older but more detailed thread about it. I wrote you a private message a few days ago so I updated this thread too. Don't know if you've seen the PM.

    Greetings,
    Vogi
  • Vote Up0Vote Down Jeff Davis
    Posts: 131
    Hi Vogi,

    I sent you an email last week. Just checking to see if you got it. :)

    Thanks!

    -Jeff
  • Vote Up0Vote Down Vogi
    Posts: 27
    Hi Jeff!

    Yes, thanks a lot for your mail!
    I replied just right now and sent you a very basic CUDA.NET example.

    I hope that at your PC Nsight 2.1 is also not working with it. ;)

    Greetings,
    Vogi
  • Vote Up0Vote Down Jeff Davis
    Posts: 131
    Hi Vogi,

    Ah, great, thanks! My spam filter picked it up, but I released it. I'll take a look.

    -Jeff
  • Vote Up0Vote Down Vogi
    Posts: 27
    Hehe.. :)
    I'm looking forward to what you find out!
    Please note that it is a very basic example though, bit it should demonstrate the problem well.

    Greetings,
    Vogi
Add a Comment