Since the SGI groups are not so active-  I thought to try my luck here.

(1) I have IRIX6.5 with CVD installed from the ProDev Workshop 2.9.3
CD.
(2) My application comprised of a few executables, which use the same
makefile: they all get compiled with:
-64 -mips4 -g

(3) After compilation, I issue "cvd <exec_name>" from the same
directory as the exec, and cvd loads.  I see in the "Status:" upper
section of the Debugger Main Window the name of the exec, the source
file name and line number. BUT the source window is empty.
The "File:" line says: "Source not available".

(4) For one out of 5 executables, I do get the source code, but for the
rest- I get what I described above.
Now, if I issue: "gdb <exec_name>", then gdb loads and show me the
source code of that executable - for all the execs!

The only reason for me to use CVD is that gdb cannot handle
posix_thread functions on IRIX (I get a "signal ?" error when gdb tries
to load an executable that has posix_thread functions), so I need cvd
to handle the executables.

I guess the issue is that cvd does not find the source code for the
execs, but I cannot figure out why - since the sturcture of my
application directories is:
<main dir>
|
|-----<Module 1 source>
|-----<Module 2 source>
|-----<Module 3 source>
|-----<makefile & execs>

So the makefile and all of the execs are located in one directory,
while the sources are in the other directories. I slinked the modules
execs from <Module X source> to the <makefile & execs> directory; and I
am running cvd from each module's directory.
If cvd can find the source for one module, it should find it for all...

Thanks for your help.

[ Post a follow-up to this message ]

sagi.perel@gmail.com writes:

> I guess the issue is that cvd does not find the source code for the
> execs, but I cannot figure out why

Most likely because of a bug in cvd.

I last worked with cvd about 5 years ago (for the same reason --
I needed to debug threaded programs), and remember it getting "lost"
quite often.

Make sure you have the latest cvd version ...

> If cvd can find the source for one module, it should find it for all...

If a program can process one set of data, it should be able to
process them all, right? Unfortunately, all programmers know that's
not the case -- bugs often show up only on particular inputs.

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.

[ Post a follow-up to this message ]

Thanks Paul.
I figured it could be a CVD bug, but it seems weird that a commercial
tool will have bugs of that magnitude.
Unfortunately, the CVD documentation does not mention this at all. They
do state how to load the source code independently- but this does not
work in my case either.
I even added my directories to the global variables CVD uses for its
search path... and still nothing.

Sagi.

[ Post a follow-up to this message ]