RE: Distributed Debugger Source Pane

["Morgan Najjar" <morgan@xxxxxxxx>]

Vadim,

> Debugger will not look for the source view and default to
> *LISTING right away if you build your modules without
> source view.

I'm not following you.  I used DBGVIEW(*ALL), thinking that would be
best to get started with.

> Line numbers in the *LISTING view will most likely not match
> the actual statement numbers. However, you should also see
> the actual statement numbers in the *LISTING view - to the
> right of the line numbers - and those should match the once
> displayed in the Call Stack properties.

Yes, there are statement numbers to the right.  These seem to be only
for executable statements, and they restart at number 1 inside of each
function.  You can't set a break with these numbers.

>
> Now, when you say that debugger  'has the correct, fully qualified,
> pathname and filename in the dialog', I wonder if it uses proper case.

I think so.  In fact I can copy/paste it to a qshell command in an
emulator session and do an "ls" command with the pasted value and see my
source file.

So it appears to be really messed up because of a line number mismatch.
I can't point to a line and set a break, and also what appears to be the
current execution line in the source pane is not so.

Something similar happens when I run the native debugger from within an
emulator session.  Here I can change views to either the "ILE C root
source view" or the "ILE C listing view".  I can set breaks ok when I'm
in the source view.  However, when I F10-Step, sometimes it appears to
step to non-executable lines, even comment lines.  I only mention this
in case there is a connection to the distributed debugger.

Ideas appreciated.

Thanks

Morgan