Re: Source/Object mismatch

Leif,

I designed the program to address vendor supplied software.
It also works pretty well when you rename a library. The
vendor used one library scheme and we used another.
If you compile with dbgview(*source) it will not change the
internal debug information. In that case my recommendation
would be to compile with dbgview *list/*all, buy your book,
or persuade you to share the technique.

David Morris

>>> leif@leif.org 02/07/02 02:08PM >>>
From: David Morris <David.Morris@plumcreek.com>
> Don't have access to your book, but you can use API's to change the
> object source information. The iseries-toolkit
> (http://iseries-toolkit.sourceforge.net)
> includes a chgobj command that allows you to change the service
> information for an object.
>
> The source for the change object API program is here:
>
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/iseries-toolkit/CVSROOT/src/qr

pglesrc/chgobjd.irp?rev=HEAD&content-type=text/vnd.viewcvs-markup
>

does it handle the following situation:
The modules are compiled with debug information,
including the original source file/members. For change
management purposes you often move the program
(including its source) to a different library for extended
testing which includes debugging at the source level.
So you would like to change the source information
of the debug stuff to point to the new library/file.
So: can the toolkit change the debug source information?
That was the problem I had to solve (and a customer
paid for it!) so I'm interested in this question. (Not
just nit-picking).