DEBUGGER VMS7.3-2

[Tim Pride]

VMS new installed, not an update. VMS 7.3-2
When I start a debug session of a C prog with SQLMOD functions in the Windows Alpha Debug64 version V7.3-200 and I display the "Help - ON Version" it displays Software version OPENVMS Debugger version V7.2 - Is this correct, or must they be the same version. I ask because when I step through the program (no step into) and it reaches a call to a sqlmod function the debugger crashes. I am lost on this, must I setup something or re-install the debugger ?

[Wim Van den Wyngaert]

I'm on 7.3 and the debug shows 7.3-01R but help on version shows 7.2.

Guess it's just a lazy programmer that forgot to adjust the help.

Wim

[Wim Van den Wyngaert]

Is there anything in debug.log ?

Wim

[Craig A Berry]

Have I understood you right that you are using the Windows debugger client? Have you tried debugging directly on the OpenVMS system and seen the same error?

[Dean McGorrill]

do an anal/image. in vms eng, by
one convention (for some) you'll see its cmsish version as the image file identification. eg on my 7.2-1 system the debugger is "X-8". You'll see image file build identification will show the result disk it was built with. in my case "X6TE-0050130100" the X6TE is a particular build, using the vms build numbering system. meaningly on the outside, but
someone inside hp could tell you what release stream your debugger was build on.
I suspect the help version is an oversight as wim suggested.
(In decnet we put the version number and left out the build id. something
more meaningful)

[Tim Pride]

In my user dir is the DEBUGERR.LOG which I attached, it looks very much like the debugger is crashing, if so should I reinstall and does that mean clossing down the system.
ps. By windows I mean DECwindows Motif!

[Wim Van den Wyngaert]

Is "sh log debugshr" showing the version in sys$share ?

Wim

[Tim Pride]

Hi Wim
I would like to do what your asking, but how do I find the version, the logical is sys$share:debugshr.exe and run it shows the debugger version etc.. that I described above, ie. V7.3-200 and the HELP->ON Version shows 7.2
regards

[Wim Van den Wyngaert]

Seems all ok to me. From which VMS version did you get sqlmod.obj and the executable itself ?

Wim

[Tim Pride]

Hi Vim,
The SQL version is RDB SQL V7.1-231
could it be something to do with set rdb$setver ?
Tim

[Wim Van den Wyngaert]

Can't say. I'm not a rdb guy (used it a few weeks in 1987, that's all).

I would make sure that everything is recompiled and relinked with the version you have on your system.

Wim

[Craig A Berry]

It sounds like you have the right debugger version for your system so that's unlikely to be the issue. System upgrades usually require a new Rdb version, so I would follow Wim's advice and rebuild your modules with tools that match your database version (if you haven't already). It could be there is an rdb$setver solution as you suggest. Any of the following might indicate whether you're pointing at the things you should be pointing at:

$ show symbol *sql*
$ show logical *sql*
$ show logical lnk$library

[Dean McGorrill]

Most Rdb spans several vms generations.
heres a pointer to the product matrix.
it looks like your version is a bit older.

http://www.oracle.com/technology/products/rdb/htdocs/rdb7/rdb_pmatrix_rdb.html

[Tim Pride]

The RDB I installed is a multi version for the v7.1-231 ( & v7.0) but I have tried to make it V7.1 and sho sym/log all show version 7.1 for exe'e and lib's.

[Dean McGorrill]

Tim,
as to debugger version, it looks like
they put something more meaningful in the
sys$share:debugshr, from an anal/image
on my 7.2-1 system..

image name: "DEBUGSHR"
image file identification: "V7.2-00R"

thats probably what they wanted to show as the real version. -Dean

[Tim Pride]

This is a known problem, Engineering are trying to find a fix.