Thanks!
I did use MCS to repair both the host and the component.
I removed both .indy files and tried again...

Still not luck - still getting the stack space error.

Chip

On Tue, 1 Oct 2019 10:50:44 -0700, Tom Benedict wrote:
> I don’t know whether this has been mentioned yet, but have you run 
> MSC on the component? Also, it’s a long shot, but have you deleted 
> the .4DIndy file? I only mention that because I’ve seen it cause 
> strange behavior.
> 
> Tom Benedict
> 
>> On Oct 1, 2019, at 07:16, Chip Scheide via 4D_Tech 
>> <[email protected]> wrote:
>> 
>> I have a component which I am trying to debug. The host is interpreted, 
>> stand alone.
>> 
>> When the component is compiled and built the host starts, but of course 
>> I can not trace the code in the component - from which I am getting an 
>> error message.
>> 
>> When I swap in the interpreted version of the component, during 
>> database startup I get an error not enough memory (obviously stuck in a 
>> loop). 
>> 
>> However, currently the very first line of code in the host ON STARTUP 
>> is TRACE.
>> The not enough memory error is presented BEFORE the trace is hit.
>> 
>> The ON STARTUP of the component is empty (no code).
>> 
>> What code could be running?
>> 
>> Thanks
>> Chip
>> ---------------
>> Gas is for washing parts
>> Alcohol is for drinkin'
>> Nitromethane is for racing 
>> **********************************************************************
>> 4D Internet Users Group (4D iNUG)
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[email protected]
>> **********************************************************************
> 
> 
---------------
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to