| Title: | DEBUG |
| Notice: | Updated locations for reporting QARs -- see note 834.1 |
| Moderator: | LOWFAT::DIETER |
| Created: | Fri Jan 24 1986 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1868 |
| Total number of notes: | 8200 |
Hello,
A cust has complained of problems with the debugger. It looks set for
an enhancement SPR but then again .... Are they doing something wrong ?
Thanks
ewan smith - uk csc.
=======================================================================
We are running VMS V6.2-1H3 on an Alpha 4100 and we have had some
trouble with the debugger. We have an image that links against a
shareable image which contains universal data symbols (defined using
globaldef in C). If we examine one of these (e.g. EXA Dgs_expanded)
while in the main image, the debugger displays a value that is garbage.
As described in the manual (section 9.4.2 etc.) we can get the correct
value by using SET IMAGE & SET MODULE commands.
My points are as follows:
1. I think it is very dangerous for the debugger to be able to display
incorrect information, indeed one of our programmers wasted a
considerable amount of time before it was realised what was happening.
The debugger must surely be able to tell that the universal symbol is
not defined in the current image and should either not display a value
or at least issue a warning message to the effect that the value is
rubbish. I have read the manual very carefully and as far I can tell
the debugger should not be exhibiting this behaviour.
2. It is very inconvenient to have to keep swapping images to see
univeral symbols in shareable images. Is there any way to avoid having
to do this? The debugger appears to have the necessary information to
be able to do this once you have issued SET IMAGE & SET MODULE the first
time. If it is not possible at the moment, it would be a highly
desireable enhancement.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1865.1 | SSPADE::ARSENAULT | Mon Jun 02 1997 17:30 | 11 | ||
For V7.1 and even more so for V7.2, the debugger does some of what you have suggested in that if it can (easily) figure out where the symbol is described, it will dynamically set module (and sometimes set image) as appropriate so that the debugger can then access that symbol correctly. For example, this works for universal symbols. However, you've described another problem in that the debugger is not only ignorant, it's incorrect. That's a little bit surprising. Certainly not acceptable. Could you provide a little example that shows this problem? | |||||