There is not enough information posted to make a diagnosis. I checked with the debugger team and they would need at least the following additonal information / data:
(1) Host GCC version (gcc â€“v)
(2) System/kernel info (uname â€“a)
(3) The binary for the test program (files can be attached to forum posts)
(4) Does starting cuda-gdb without any arguments result in the same behavior?
$ gcc -v
Using built-in specs.
Configured with: ../gcc-4.4.0/configure --prefix=/gcc/4.4.0/x86_64 --with-gmp=/gmp/4.3.1/x86_64 --with-mpfr=/mpfr/2.4.1/x86_64
Thread model: posix
gcc version 4.4.0 (GCC)
$ uname -a
Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5)
Copyright (C) 2009 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-redhat-linux-gnu".
For bug reporting instructions, please see:
Python 2.7.2 (default, Aug 8 2011, 10:58:53)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-50)] on linux2
Type "help", "copyright", "credits" or "license" for more information.