× 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.


  • Subject: debug information for module
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Thu, 12 Jul 2001 13:27:46 -0500

Folks,

Here is a question for the experts:

When you create a (RPGLE) *MODULE object,
information about the source file/member/library
seems to be stored in the OIR (the object information
repository) and also in a secondary associated space
(address of which is hidden at offset x32 in the
object - not the space - of the primary associated
space), thus in TWO places. This is already bad enough
(not normalized data), but here is the problem:

If you change the source information (e.g. the library -
which is a very meaningful change) in both places
and then bind the module into a program, the debugger
somehow still seems to find the original source information
and insists on using that source, disregarding both the
OIR and the HLL FILE DESCRIPTOR in the secondary
space. Is this "working as designed" and if so is there
yet a third place where this information is stored?
Where is the debugger actually looking?




+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

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.