Home/ Questions/Q 8710773
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T04:42:38+00:00

I installed cuda 5 on my Ubuntu 12.10 64 bits. I have a GTX

  • 0

I installed cuda 5 on my Ubuntu 12.10 64 bits. I have a GTX 675M, so I’m using bumblebee to run apps on my cuda device. I’m running nsight through bumblebee (optirun):

frederico@zeus:~$ optirun /usr/local/cuda/libnsight/nsight

And it works just fine, I can compile and execute applications. The problem is when I try to use cuda-gdb in nsight, I got the following error when click on debug button:

No source available for "main() at 0x403c6f"

But if I try to use cuda-gdb on console it works:

frederico@zeus:~/Dropbox/coisas/projetos/delta_cuda$ optirun cuda-gdb bin/linux/release/gpu_md5 
NVIDIA (R) CUDA Debugger
5.0 release
Portions Copyright (C) 2007-2012 NVIDIA Corporation
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/frederico/Dropbox/coisas/projetos/delta_cuda/bin/linux/release/gpu_md5...done.
(cuda-gdb) run
Starting program: /home/frederico/Dropbox/coisas/projetos/delta_cuda/bin/linux/release/gpu_md5 
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff1dfe700 (LWP 10437)]
[New Thread 0x7ffff07f7700 (LWP 10438)]
[New Thread 0x7fffb07f6700 (LWP 10439)]
[New Thread 0x7fff6bfff700 (LWP 10440)]
[New Thread 0x7fff23fff700 (LWP 10441)]
[New Thread 0x7ffedbfff700 (LWP 10442)]
[New Thread 0x7ffe93fff700 (LWP 10443)]
[New Thread 0x7ffe4bfff700 (LWP 10444)]
[New Thread 0x7ffe03fff700 (LWP 10445)]
[Thread 0x7ffe03fff700 (LWP 10445) exited]
[Thread 0x7fffb07f6700 (LWP 10439) exited]
[Thread 0x7ffe4bfff700 (LWP 10444) exited]
[Thread 0x7fff23fff700 (LWP 10441) exited]
[Thread 0x7ffe93fff700 (LWP 10443) exited]
[Thread 0x7ffedbfff700 (LWP 10442) exited]
[Thread 0x7ffff07f7700 (LWP 10438) exited]
[Thread 0x7fff6bfff700 (LWP 10440) exited]
[Thread 0x7ffff1dfe700 (LWP 10437) exited]

Program exited with code 030.
(cuda-gdb)

Any idea of what can be going on?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    That message gets printed when your application suspends. It means your application was not compiled with debug information – in this case debugger is not able to map your instructions to the source lines.

    To reproduce this message in the command-line cuda-gdb you need to suspend on a breakpoint, e.g. do “break main” before doing “run”

    Update – for people who have similar problem sometime in the future

    Application was built as follows:

    1. CUDA kernel code was compiled with NVCC and included debug information. E.g. NVCC call was: nvcc -g -G -c mykernel.cu -o mykernel.o
    2. This object file was linked with other object files that were compiled by GCC without generating the debug information – g++ mycpp1.cpp mycpp2.cpp mykernel.cu -o mycudaapplication. This resulted in some partial debug information that was not enough for cuda-gdb to properly resolve the path.

    Nsight Eclipse Edition by default is relying on cuda-gdb source path resolution to find a file to open in an editor when debugging CUDA application.

    • 0