Sorry you are having troubles with PGDBG. There are a few things you could do to help diagnose the problem.
The first thing to check on Mac OS X is that the debugger will run with group “procmod” privileges. This is supposed to be handled during installation, but perhaps in your case it wasn’t. That can be accomplished in two ways:
(1) you are a member of group procmod
(2) the permissions on the executable named “pgdebug” should be “setgid procmod”
In addition, the debugger executable must be installed on a local drive.
This is all due to Mac OS X security requirements.
To see if you are a member of group procmod, run
and look to see if procmod shows up in the list.
To see if the debugger (an executable named “pgdebug”) has “setgid procmod” permissions, you can run the following commands:
$ which pgdebug
$ ls -l `which pgdebug`
-rwxrwsr-x 1 myname procmod 12820680 Jan 6 16:00 /usr/pgi/osx86-64/10.1/bin/pgdebug*
Note that it is owned by group procmod and the setgid bit is set (that is the ‘s’ in rwxrwsr-x).
To see if the debugger is on a local drive, use the ‘df’ command on the directory where the “pgdebug” executable is located:
If the Filesystem in the output looks something like /dev/disk0s2, it is a local filesystem and should be OK. If it looks more like foo.bar.com:/vol/vol5/dir1, then it is a network drive, and that is a problem.
Other things of interest: what version of Mac OS X are you running (10.4/Tiger, 10.5/Leopard, 10.6/Snow Leopard)? Select the About box under the Apple menu to find this information.
As to your other questions:
(1) can you re-use the dSYM directory - unfortunately, at this time pgdbg regenerates it for every debug session.
(2) is it a 64-bit vs 32-bit issue - it’s possible but seems unlikely given the symptoms you describe.
Let us know what you find out. We want to get you up and running!