Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!rutgers!sri-spam!mordor!lll-tis!ptsfa!ihnp4!chinet!ward
From: ward@chinet.UUCP (ward)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Has anyone heard of Parascope debugger for Turbo C ?
Message-ID: <1242@chinet.UUCP>
Date: Mon, 29-Jun-87 13:54:22 EDT
Article-I.D.: chinet.1242
Posted: Mon Jun 29 13:54:22 1987
Date-Received: Wed, 1-Jul-87 01:30:34 EDT
References: <303@qtc.UUCP>
Reply-To: ward@chinet.UUCP (Ward Christensen-)
Organization: Chinet - Public Access Unix
Lines: 16
Keywords: TurboC Debugger Periscope

> The Periscope debugger as mentioned by Borland for Turbo C?
  Its from "The Periscope Company" (formerly "DataBase Decisions")
14 Bonnie Lane, Atlanta GA 30328, (404) 256-3860.  See my review in
the March '86 issue of PC Tech Journal.
  Its called Periscope because it "surfaces" to "snoop around" via a
breakout button (tied to NMI).  I have Turbo C, but have not done enough
with it yet to comment on Periscope use with it.  I HAVE used Periscope
with Lattice C and have gotten interleaved source lines.  My ONE test
with Turbo C had a minor problem: they would "emit" line labels to the
object module with the same address for two lines, i.e. if you split an
"if" across multiple lines, each line would have the same address in the
symbol table.  Periscope had apparently not seen that before, and thus
showed only the first line - thus you didn't really see all your source
code when debugging.  I mentioned this to Borland and did not receive
specific feedback on it, but received "general" feedback on multiple
issues, saying "we have addressed all your concerns".