Databases
StackOverflow2013
Postsdbo
POQt and CUDA VIsual Profiler error in memory transfer size
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQt and CUDA VIsual Profiler error in memory transfer size
    primarykey
    data
    text
    <p>I've prepared a .pro file for use Qt and CUDA in a linux machine (64bits). When I run the application into the CUDA profiler, the app executes 12 times but before present the results i get the next error: </p> <blockquote> <p>Error in profiler data file '/home/myusername/development/qtspace/bin/temp_compute_profiler_0_0.csv' at line number 6 for column 'memory transfer size.</p> </blockquote> <p>The main.cpp file is as simple as</p> <pre><code>#include &lt;QtCore/QCoreApplication&gt; extern "C" void runCudaPart(); int main(int argc, char *argv[]) { QCoreApplication a(argc, argv); runCudaPart(); return 0; } </code></pre> <p>The fact is that if i remove the "QCoreApplication a(argc, argv);" line the CUDA Visual Profiler works as excepted and show all the results.</p> <p>I've checked that the cuda_profile.log is generated from the command line if i export the CUDA_PROFILE=1 environment variable. The comma-separated file is also generated if i export the COMPUTE_PROFILE_CSV=1 variale <em>but</em> the CUDA Visual Profiler crashes when i try to import that file.</p> <p>Any hints about this issue? It seems something related to the CUDA visual Profiler application not with the code.</p> <p>If you are wondering why i did a so simple main.cpp with Qt but without using Qt :P is that i would like improve the framework in the future to add a GUI.</p> <p>// details of CUDA, GPU, OS, QT, and compiler versions</p> <pre><code> Device"GeForce GTX 480" CUDA Driver Version: 3.20 CUDA Runtime Version: 3.20 CUDA Capability Major/Minor version number: 2.0 OS: ubuntu 10.04 LTS QT_VERSION: 263682 QT_VERSION_STR: 4.6.2 gcc version 4.4.3 nvcc compilation tool, release 3.2, V0.2.122 </code></pre> <p>I've noticed that the problem is with the <strong>QCoreApplication construct</strong>. It does something with the arguments. If I modify the line as:</p> <pre><code>QCoreApplication a(); </code></pre> <p>the Visual Profiler works as excepted. Hard to know what is happening and if this change will be a problem in the future. Any hints?</p> <p>Regarding to the QCoreApplication construct the example also work if I call the cuda part before the QCoreApplication.</p> <pre><code>// this way the example works. runCudaPart(); QCoreApplication a(argc, argv); </code></pre> <p>Thanks in advance.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpQB
    1. USpQB
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POQt and CUDA VIsual Profiler error in memory transfer size
      1. USben
      1. VTFavorite
    2. VO
      singulars
      1. POQt and CUDA VIsual Profiler error in memory transfer size
      1. USpQB
      1. VTBountyStart
    3. VO
      singulars
      1. POQt and CUDA VIsual Profiler error in memory transfer size
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe application invokes a kernel launch and memory transfers. The application releases _all_ resources. The application exits normally (return cudaThreadExit()). Any hints. Thanks!
      singulars
      1. POQt and CUDA VIsual Profiler error in memory transfer size
      1. USpQB
    2. CODid you check the csv file? Is it correct or corrupted? You could try opening it in Excel or something similar.
      singulars
      1. POQt and CUDA VIsual Profiler error in memory transfer size
      1. USBart
    3. CO@Bart The csv file is fine. I can open it with OpenOffice Calc or any text editor. Thanks!
      singulars
      1. POQt and CUDA VIsual Profiler error in memory transfer size
      1. USpQB
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload