ed@qtc.UUCP (Ed Lisle) (06/23/87)
I talked to Borland today concerning some of the bugs posted on
the net and they are shipping patches and future patches later on
to me. All you have to do is call.
Tech support: (408) 438-8400 (have your s/n ready)
Anyway, while talking to tech support I asked if they are developing
a debugger for Turbo C. He could not comment but did recommend using
Parascope and mention'd that some users prefer'd this over codeview.
I like codeview, expect for compile speed and codeview not understanding
how to dump structures very well.
Has anyone used, heard, any comments, on this debugger. Also who
markets this product and how much.
Thanks.
+------------------------------------------------------------+
| Ed Lisle | ogcvax! |
| Quantitative Technology Corporation | verdix! qtc!ed |
| Beaverton, OR (503) 626-3081 | sequent! |
+------------------------------------------------------------+ward@chinet.UUCP (ward) (06/29/87)
> 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". cma@bentley.UUCP (CM Ackerman) (06/30/87)
I think you're talking about the Periscope Debugger. Here are my impressions:
I use CodeView for most of my application programming but when the bugs get
serious, I use (Excedrin &) Periscope.
Disclaimer: I have no interest in any of the products mentioned below
except as a usually satisfied user.
Best feature is that Periscope is resident eliminating
"Works in the debugger but not by itself" problems
since your program is always loaded at the same spot in memory.
You can also give up features for memory.
So when CodeView can't load your program because there's not enough memory
for you and it, you can still use a stripped down version of Periscope.
The Next best feature is excellent "tech support".
I use CodeView for general nonserious stuff because it's got one
big advantage over everybody elses debugger:
Access and display of local variables and expressions. - Can't beat that.
(But don't bother asking their "tech support" for advice).
Periscope comes with a "Submarine" board (I'm not kidding).
with some protected memory for those applications that might clobber
the debugger if it's in regular memory, and it's got a breakout switch
to generate NMI when your keyboard gets locked.
With the board it's about $300, it's called Periscope I and is solid as a rock,
without the board it's about $100 and its called Periscope II-X.
The breakout switch alone version is about $150 and is called Periscope II.
I got it rather quickly from Programmer's Connection (1-800-336-1166).
(Also Periscope Co., 14 Bonnie Lane, Atlanta GA 30328,1-404-256-3860)
They also make a board (which I've never used) (for cheap emulator users?)
for about $1000 that does H/W breakpoints.
C. Ackerman ihnp4!bentley!cma
Bell Labs, Rm 3F341, 200 Laurel Ave, Middletown, NJ 07748