From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-cs!stachour
From: stachour@umn-cs.CS.UMN.EDU (Paul Stachour)
Newsgroups: comp.lang.ada
Subject: Re: User requirements on generics
Message-ID: <10479@umn-cs.CS.UMN.EDU>
Date: 17 Dec 88 17:06:01 GMT
References: <8812161453.AA02985@aries>
Reply-To: stachour@umn-cs.cs.umn.edu (Paul Stachour)
Organization: CSci Dept., University of Minnesota, Mpls.
List-Id: <comp.lang.ada>

In article <8812161453.AA02985@aries> emery@ARIES.MITRE.ORG (David Emery) writes:
>  ... 
>Note that code sharing can affect the debugger's ability to do this.
>If code sharing for STACK_PACKAGE is true, then the debugger may not be
>able to support setting a breakpoint inside a specific instance.  

Dave, I don't see why this must be true.   From the debuggers's viewpoint,
one sets a breakpoint in the shared-code for the generic.  When the 
breakpoint is hit, the debugger checks the context of the breakpoint
with respect to who did the calling from what line, etc., and thus can
determine from the symbol-table info which instance of the generic that
it is actually in.  The breakpoint is "taken" if that is the instance
in which the breakpoint was set, otherwise the breakpoint is "ignored".
  ...Paul