RE: Follow up: What else....

[Keith Knapp]

Hello all. 

Solution to problem # 2 found,  

Action: Starting a program with ddd
Results: An error message stating the ddd.vsl could not be loaded.
Cause: DDD_HOME variable not set.
Resolution: Set DDD_HOME to point the folder containing the fold vsllib.

Keith


-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of R. Bernstein
Sent: Tuesday, 16 January 2007 12:18 PM
To: Discussion list for DDD,the GNU graphical debugger front end
Subject: RE: Follow up: What else....

Basically what strace is saying that when you run stat() or stat64() for
that ddd.vsl it gets that ENOENT. If other programs in the directory work,
then it would point more to a permission problem on that file entry. It
could also be that directory info is out of date or "stale" (e.g. if this
were located on NFS). And you may need to take into account the uid/gid that
ddd is running under. You could also write a little C program that issues
the stat() directly to compare results.

Sorry, I don't know what to say. But one thing that seems pretty clear is
that the problem is with your setup rather than ddd.


Keith Knapp writes:
 > Hey Rocky and everyone else,
 >
 > 1. I thought of and checked file permissions immediately after sending
the  > last email and they are not the problem.
 >
 > 2. I ran strace and it returns:
 >      -1 ENOENT (No such file or directory)
 > for every location of the file ddd.vsl it tries, and as I mentioned
before  > it tries about 20 different spots. I still have the file in 2
locations.....
 >
 >
 > It doesn't make sense. I get no error messages for any of the other files
in  > the vsllib directory. I would have thought that if ddd.vsl doesn't
load  > other modules may have issue too. 
 >
 > Keith
 >
 >
 >
 > -----Original Message-----
 > From: address@hidden
 > [mailto:address@hidden On Behalf Of R. Bernstein
> Sent: Tuesday, 16 January 2007 10:20 AM  > To: Discussion list for DDD,the
GNU graphical debugger front end  > Subject: RE: Follow up: What else....
 >
 > Keith Knapp writes:
 >  > Andrew,
 >  >
 >  > I didn't know the ~/.ddd/log existed, I guess everything is logged in
>  > Linux....
 >  >
 >  > The logs says it tries to find ddd.vsl in about 20 different
locations,  > > (even the one in which the file is actually located) and
then it says: 
 >  >     #  Searching "vsllib/ddd.vsl"...not found.
 >  >     !  Could not load VSL Library "vsllib/ddd.vsl"
 >  >
 >  > So I tried copying the file to another of the 20 locations it looks
for  > it  > and it still gives the error above.
 >  > Why would it not be able to find a file in either of two directories
it  > is  > looking for it in? 
 >
 > The obvious thing that comes to mind is file permissions. :-)  >  > If
you want the hacker way to verify the file is getting opened properly or  >
not, you could run strace and look for the return code on the stat() or  >
stat64() system call  >  > write(5, "#  Trying \"/home/rocky/.ddd/vsll"...,
44) = 44  > stat64("/home/rocky/.ddd/vsllib/ddd.vsl", 0xbf8d1a5c) = -1
ENOENT (No such  > file or directory)
stat64("/home/rocky/.ddd/vsllib/ddd.vsl", 0xbf8d1a5c) =  > -1 ENOENT (No
such file or directory) write(5, "#  Trying  > \"/usr/local/share/ddd-"...,
64) = 64  > stat64("/usr/local/share/ddd-3.3.12-test6cvs/vsllib/ddd.vsl",
 > {st_mode=S_IFREG|0644, st_size=8209, ...}) = 0  >  >  > From:
address@hidden
 >  > [mailto:address@hidden On Behalf Of Andrew  >
Gaylard  > Sent: Monday, 15 January 2007 9:44 PM  > To: Discussion list for
> DDD,the GNU graphical debugger front end  > Subject: Re: Follow up: What
> else....
 >  >
 >  >
 >  >
 >  > On 1/15/07, Keith Knapp <address@hidden> wrote: 
 >  >
 >  > Andrew,
 >  >
 >  > Thanks for the response. Good questions....
 >  >
 >  > 1. Yes GDB is installed. 
 >  >     Version: GNU gdb Red Hat Linux (6.3.0.0-1.132.E)
 >  > 2. "which gdb" returns: /usr/bin/gdb  >  > 3. Yes my path contains
/usr/bin  >  > 4. When I just run "gdb sample"  gdb starts fine and
functions properly.
 >  >
 >  >
 >  > Keith,
 >  >
 >  > This is pretty wierd.
 >  >
 >  > Does your ~/.ddd/log show anything?
 >  >
 >  >
 >
 >
 >