home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!walter!att-out!pacbell.com!decwrl!pa.dec.com!engage.pko.dec.com!nntpd.lkg.dec.com!persis.enet.dec.com!finlayson
- From: finlayson@persis.enet.dec.com (Mark A. Finlayson)
- Subject: Re: PCA limitation / Unix "strip" for VMS
- Message-ID: <1993Jan25.161718.22866@nntpd.lkg.dec.com>
- Keywords: PCA,strip
- Lines: 29
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Reply-To: finlayson@persis.enet.dec.com (Mark A. Finlayson)
- Organization: Digital Equipment Corporation, Nashua, NH
- References: <418@ittc.wec.com>
- Date: Mon, 25 Jan 1993 16:17:18 GMT
-
-
-
- In article <418@ittc.wec.com>, fitch@ittc.wec.com (Ken Fitch) writes:
- |> The DECset Performance & Coverage Analyzer (PCA) is having trouble
- |> digesting an executable with a large number of debug symbols.
- |> When run it gives the message:
- |>
- |> =================================================================
- |> /user/krf/appr_bm> run testexec_pca
- |>
- |> VAX PCA Collector Version V4.0-80
- |>
- |> PCAC> g
- |> %PCA-E-INCDST, incorrect DST nesting in module RPDINIT. Datafile not set.
- |> %PCA-I-NODATACOL, exiting with no data collection phase
- |> =================================================================
- |>
- |> (Note that the pathname prompt simply betrays my Unix orientation.)
-
- I'm not a PCA developer and can't give you an authoritative answer but
- usually the incorrect DST nesting message indicates that there's something
- wrong with the DSTs for that module. I don't know what is causing your
- specific problem, but you can usually work around these by compiling the
- modules in question with /NODEBUG (RPDINIT in your case).
-
- Mark Finlayson
-
- My opinions are not the opinions of Digital Equipment Corporation
-
-