Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!uunet!dg!dg-rtp.dg.com!bkahn
From: bkahn@archive.webo.dg.com (Bruce Kahn)
Newsgroups: comp.sys.apple2
Subject: Re: Q: Prizm and multi-segmented files
Keywords: C, Orca/C, prizm
Message-ID: <1031@dg.dg.com>
Date: 8 Oct 90 14:27:14 GMT
References: <1023@dg.dg.com> <14027@smoke.BRL.MIL>
Sender: root@dg.dg.com
Reply-To: bkahn@archive.webo.dg.com (Bruce Kahn)
Organization: Data General Corporation, Westboro, MA
Lines: 38

In article <14027@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
|> In article <1023@dg.dg.com> bkahn@archive.webo.dg.com (Bruce Kahn) writes:
|> >Has anyone been able to debug segmented (desktop) programs under Prizm?
|> >Any ideas (besides cumbersome fprintf's)??
|> 
|> fprintf() won't do you any good in a desktop application.

  I use:

#ifdef DEBUG
fprintf(debug_fp, "Filename = <%s>\n", replyPtr->filename); 
#endif

  This works wonders for tracking variables (globals or locals) across various
modules.  Granted its crude but at least you get a trail to follow and can do
SOME debugging...

|> 
|> I haven't tried exactly the scenario you describe, but I have managed
|> to successfully use the ORCA debugger with ORCA/C 1.1 under other
|> circumstances.  Make sure the COMPILE option is set to generate debugger
|> code (this consists of some COP opcodes followed by data for the
|> debugger), and you may have to create an EXE link output instead of a
|> SYS16 output.  Note also there is a "graphics window" that you're expected
|> to open via one of the menu options if your program uses the display.

  Can an EXE have resources in it?  Since I use duplicate -d and duplicate -r
to merge the forks, can I do this under prizm (apart from running my 'make' 
scripts in the Shell window)?  I didnt think that duplicate would touch a file
that was not of type S16 (I recall having to use change foo.dfork s16 after
I did the link using ZapLink).  Guess Ill have to peek at the sample Bullseye
program to see about this 'graphics window'.

--
                                          Bruce (bkahn@archive.webo.dg.com or
                                                 kahn@adam.dg.com)
  
  Standard disclaimers apply, except where prohibited by law...