[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::debug

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

1868.0. "Many breakpoints, slow, expmempool, intmemerr??" by KERNEL::PULLEY (Come! while living waters flow) Tue Jun 03 1997 13:28

Hi,

I've a customer running OpenVMS v6.2 Alpha, Debug v6.2-102r.
(The images in the Alpha are native).
He's tryed this on a VAX v5.5-2, and works without problem.

He is trying to set about 1500 break points in a shareable image.
He gets as far as about 500, then, the Debugger expands the memory pool, and
starts going slow--(I think he said about 15 break points an hour).
This happens whether in character cell or windows.

So, he tryed doing a stop, and got the following Debug log:-
@isaac_all.dbg
!%DEBUG-I-EXPMEMPOOL, expanding debugger memory pool
!%DEBUG-I-EXPMEMPOOL, expanding debugger memory pool
go
!%DEBUG-I-DYNIMGSET, setting image DEBUG_ISAAC
!%DEBUG-I-SRCNOTCURAV, source code for line 689 in module MAIN not currently
available.
!break at routine MAIN\main
go
!%DEBUG-I-DYNIMGSET, setting image ISAAC_SQLSHR
!%DEBUG-W-SCRNOSRCLIN, no source line for address 0196CFF8 for display in Source
View
!break at routine ISAAC_SQL_G002_ACCRTD_ROTXN
!%DEBUG-W-SCRNOSRCLIN, no source line for address 0207AB0C for display in Source
View
!%DEBUG-W-SCRNOSRCLIN, no source line for address 01969C18 for display in Source
View
!break at routine ISAAC_SQL_G001_ROLLBACK
!%DEBUG-W-SCRNOSRCLIN, no source line for address 02089AA0 for display in Source
View

step/return
!%DEBUG-W-SCRNOSRCLIN, no source line for address 01EF3604 for display in Source
View

SET SCOPE/CURRENT %DEC 0
!%DEBUG-W-SCRNOSRCLIN, no source line for address 01EF3604 for display in Source
View
SET SCOPE/CURRENT %DEC 2
!%DEBUG-W-SCRNOSRCLIN, no source line for address 0207DF84 for display in Source
View
step/in
!%DEBUG-W-SCRNOSRCLIN, no source line for address 0207AAB4 for display in Source
View
!stepped to 34056884
step/in
!
!This is being written to log file DEBUG.LOG
!
!The following information may be helpful to the DEBUG maintainers.
!
!If you wish to report this problem please include:
!
!     o The stack dump that follows.
!     o The debugger version number.
!     o The program being debugged, both source and image.
!     o The last, if not all, commands entered to the debugger.
!     o Any other information that may be helpful.
!
!The version of the debugger is: OpenVMS Alpha DEBUG Version V6.2-102R
!
! module name     routine name                     line       rel PC    abs PC
! SHARE$DEBUG                                                00000000  01EE7218
! SHARE$DEBUG                                                00000000  01F160A4
!----- above condition handler called with exception 0002A284:
!%DEBUG-F-INTMEMERR, internal memory-pool error
!----- end of exception message
!                                                            00000000  9E6FA2BC
! SHARE$DEBUG                                                00000000  01EFE54C
! SHARE$DEBUG                                                00000000  01EEE4C0
! SHARE$DEBUG                                                00000000  01EEE0C0
! SHARE$DEBUG                                                00000000  01EE5D6C
! SHARE$DEBUG                                                00000000  01F12448
! SHARE$DEBUG                                                00000000  01F11E08
! SHARE$DEBUG                                                00000000  01F0CEB0
! SHARE$DEBUG                                                00000000  01EE60B0
! SHARE$DEBUG                                                00000000  01EE5440
! SHARE$DEBUG                                                00000000  01EF2A6C
!----- above condition handler called with exception 0000000C:
!%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000099,
PC=0207AAC0, PS=00000018
!----- end of exception message
!                                                            00000000  9E6FA2BC
! SHARE$DEBUG                                                00000000  0207AAC0
!----- above condition handler called with exception 0000043C:
!%SYSTEM-F-OPCDEC, opcode reserved to Digital fault at PC=0207DF84, PS=0000001B
!----- end of exception message
!                                                            00000000  9E6FA2BC
! SHARE$DEBUG_ISAAC 
!                                                            00000000  0207DF84
! SHARE$DEBUG_ISAAC 
!                                                            00000000  007F2C78
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002FAFC0
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002FB3EC
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002D87D8
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002CBF14
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002CBD10
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002C00A4
! SHARE$DEBUG_ISAAC 
!                                                            00000000  002C0054
! SHARE$DEBUG_ISAAC 
!                                                            00000000  00B7E75C
!                                                            00000000  9E8141F8

Thanks for any suggestions or comments,
Steve.
T.RTitleUserPersonal
Name
DateLines
1868.1not sure...and knownSSPADE::SSPADE::HILDETue Jun 03 1997 18:4519
I don't know why setting breakpoints would slow down.  I suspect
this is a quota problem of some sort.  Perhaps he is thrashing...perhaps
his working set is too small.  Expanding memory on ALPHA will eat up
more virtual memory since the expansions will always be multiples of
the CPU-specific page size...8K for ALPHA versus 512 bytes for VAX.  I
don't observe the slow down in my attempts to replicate this.

Steps after debug kernel memory expansion will likely fail as observed.
I can replicate the OPCDEC...this is a known problem fixed in V7.0 but
never ECOed into V6.2.  There is no work around other than avoiding the
memory expansion.  Up until now, we've only observed this problem with
watchpoints set on large data structions, e.g. arrays, since those resolve
into individual watchpoint events on all the basic elements, e.g. array
members/elements.  In this case, the customer would be forced to set less
breakpoints or cancel and set smaller sets of breakpoints as needed.

Lon