× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Morgan,

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

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.

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

Regards,
Vadim
Internet:  berestet@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.






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.