Conference clusta::acms

4097.0. "problems seeing source from debugger" by CSC32::J_HENSON (Don't get even, get ahead!) Thu Feb 06 1997 16:55

I know that this is a real blast from the past, but I'm working a server
debugger issue for acms v3.3b on openvms v6.1/vax, and need to know
if this is a known issue.

My customer is trying to debug a running server, written in cobol.  He
is able to successfully attach to the server with the debugger, and
set breakpoints, etc.  His problem is that he cannot see the source
code from the debugger for the first cobol module called by the
task.  And, to make things even stranger, once the first module
calls another routine, he can see the source of the second and
subsequent routines.  It's just the first routine/procedure for
which he cannot see the source.

Of course, he swears that he is compiling the problem module with
/debug and linking correctly, and that the source is in an
available location.  He has also tried using the set source command,
but that hasn't helped.

I think that it's more of a debugger, cobol issue, but thought I
would check here just to make sure I'm not overlooking a known
problem.

Thanks,

Jerry

    
    	If the customer uses the task debugger, can he/she see the
    	source for the first module called?
    
    	Bill