RE: Distributed Debugger Source Pane

[xuanchen@xxxxxxxxxx]

Morgan,

See my answer below.

Thanks,

Xuan Chen, Debug for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@ca.ibm.com



"Morgan Najjar" <morgan@appx.com>@midrange.com on 01/18/2002 12:53:41 PM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   <code400-l@midrange.com>
cc:
Subject:  RE: Distributed Debugger Source Pane


Xuan,

Ok, that helps.  I still have a mismatch on the line numbers, which I'm
investigating now.  Could this have something to do with the fact that
these C source files were tar'd on unix and untarred onto the AS400?  I
originally untarred them into the root file system, and then later moved
them to the QOpenSys file system.

Answer:
   Could you check if that is the case for listing view? If not, please
   show me what
   kind of statement it is.  Thanks.

I still get the "can't find source" dialog for each source file, with
the /QOpenSys pathname in the dialog.  I then have to replace it with
the pathname on my local pc and then the source listing displays.  Is
there a way to default this, so that I don't get this error?  I did
place the local source path in the "Debugger Settings" dialog as you
suggested.

Answer:
   If you put the correct mapped IFS path (in PC) into your local source
   path entry of the Debugger Settings dialog, you should be able to get
   the source.  Note:  It is the path where your source resides, and it
   assume the name of the source be "moduleName.c".

   e.g., if you module name is myModule, and the local source path is set
   to z:\myDir, the debugger will try to find source file myModule.c in
   directory z:\myDir.

   If you still cannot find the source by using the rule described above,
   it is a bug.  Please let us know.  Thanks.


Thanks

Morgan

> -----Original Message-----
> From: code400-l-admin@midrange.com
> [mailto:code400-l-admin@midrange.com]On Behalf Of xuanchen@ca.ibm.com
> Sent: Thursday, January 17, 2002 4:40 PM
> To: code400-l@midrange.com
> Subject: Re: Distributed Debugger Source Pane
>
>
> Morgan,
>
> The IFS source path support for Debugger is currently only
> available for
> Java.  For C/C++, you probably have to map a drive in your PC
> to IFS, and
> put the mapped path in Local Source Path entry of the
> Debugger Settings
> dialog.
>
> We are considering putting IFS source path support for
> languages other than
> Java in next release.
>
> Regarding to setting breakpoints for source location related
> to a specific
> call stack entry, try to click on that entry (in the call stack).  The
> cursor should point to that location in the debug view (could
> be source
> view, listing view or statement view, depending which view you are
> currently display).  Then you could set breakpoint by double
> clicking or
> using the Set Line Breakpoint dialog.
>
> Thanks,
>
> Xuan Chen, Debug for iSeries
> (905) 413-3769 T/L 969-3769
> xuanchen@ca.ibm.com
>
>
>
> "Morgan Najjar" <morgan@appx.com>@midrange.com on 01/17/2002
> 11:54:40 AM
>
> Please respond to code400-l@midrange.com
>
> Sent by:  code400-l-admin@midrange.com
>
>
> To:   <code400-l@midrange.com>
> cc:
> Subject:  Distributed Debugger Source Pane
>
>
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Greetings again.
>
> Well, I finally got the distributed debugger running
> (although I had to
> utilize a local pc and circumvent the firewall and ports issues).
>
> Two different questions, that I'm hoping someone can address easily.
>
> 1) My C source is all in stream files in the QOpenSys file
> system.  Each
> time the distributed debugger starts it gives me an error
> that it can't
> find
> my source.  It has the correct, fully qualified, pathname and
> filename in
> the dialog, and the source file is really there, but the
> debugger complains
> about it.  If I just click cancel on that dialog, it proceeds
> anyway but
> must switch to the "listing" view, because I can see my source fine.
>
> Before loading the program, I also tried clicking on the "Debugger
> Settings"
> button, and specifying the IFS pathname, but that did not
> seem to help.
>
> So the question here are (1) why doesn't it find the source
> file, or (2)
> can
> the debugger be told to default to "listing" view so I don't get the
> errors?
>
> I suspect that this issue has something to do with my second problem:
>
> 2) The line numbers that appear in the source pane (listing
> view) don't
> seem
> to match up with the statement number that appears in the call stack
> properties, nor do they seem valid for setting breakpoints.
> Does "source"
> have to be the view, and not "listing" in order to have the
> proper line
> numbers?
>
> Thanks
>
> Morgan
> --
>
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
> or email: CODE400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/code400-l.
>
>
>
>
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
> or email: CODE400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/code400-l.
>

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.