Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!unmvax!ncar!ames!killer!pollux!ti-csl!m2!holland
From: holland@m2.csc.ti.com (Fred Hollander)
Newsgroups: comp.sys.mac.programmer
Subject: Re: List Manager Problem
Keywords: combining text and graphics.
Message-ID: <66569@ti-csl.CSNET>
Date: 31 Dec 88 17:41:09 GMT
References: <221@dalcsug.UUCP> <966@geowhiz.UUCP> <1235@viscous> <896@husc6.harvard.edu>
Sender: news@ti-csl.CSNET
Reply-To: holland@m2.UUCP (Fred Hollander)
Organization: TI Computer Science Center, Dallas
Lines: 20

In article <896@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
>In article <1235@viscous> jamesm@sco.COM (James M. Moore) writes:
>>Is there a way to use the Lightspeed C debugger to debug custom LDEFs?
>
>	I usually implement custom defprocs by creating a dummy defproc
>resource that's only six bytes long, containing $4EF9 0000 0000, and at
>program startup, I patch the last four bytes to point at my custom defproc
>which is implemented as a procedure in my program.

That sure is a lot easier than building the defproc in a seperate project
and then copying the resource to the application's project.  Thanks for the
tip.  But, don't tell me (it would be too good to be true) that you can
now debug the defproc at source level.

Fred Hollander
Computer Science Center
Texas Instruments, Inc.
holland%ti-csl@csnet-rela

The above statements are my own and not representative of Texas Instruments.