[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

1849.0. "inhibit %DEBUG-I-SOURCESCOPE [...] messages?" by COMEUP::SIMMONDS (loose canon) Wed Mar 19 1997 19:19

    [OpenVMS Alpha DEBUG Version V7.1C-000 on OpenVMS Alpha V6.2-1H3]
    
    Dear Debug mavens.. Is there a means of inhibiting the output to the
    DebugSource*MessageOutputPanel of all three messages:
    
    %DEBUG-I-SOURCESCOPE, Source lines not available for .0\%PC
            Displaying source in a caller of the current routine
    %DEBUG-I-SOURCESCOPE, Source lines not available for .0\%PC
            Displaying source in a caller of the current routine
    %DEBUG-I-SOURCESCOPE, Source lines not available for .0\%PC
            Displaying source in a caller of the current routine
    
    which are output on _each_ single-instruction step when stepping
    through, for example, an RTL routine in SHARE$LIBRTL_CODE0.. ?
    
    Only ask because it clutters the output to the window and it's harder
    to see the machine code control flow.. (which is what I'm really
    interested in)    B.t.w., it makes no diff. if STEP is set SILENT.
    
    Many thanks,
    John.

T.R	Title	User	Personal Name	Date	Lines
1849.1		SSPADE::SSPADE::HILDE		`Fri Mar 21 1997 15:06`	5
	There is on way currently that I know of to inhibit or redirect these messages...sorry. Lon
1849.2	complexity?	COMEUP::SIMMONDS	loose canon	`Sat Mar 22 1997 20:26`	5
	Re: .1 Oh, that's disappointing news.. thanks anyway Lon. John.