[Cuis-dev] White VM window

[Juan Vuletich]

Hi Hilaire,

On 8/17/2022 11:49 AM, Hilaire Fernandes via Cuis-dev wrote:
>
> Hi Juan,
>
> At first I got a DNU when executing this snippet, but now ok. Whatever.
>
> In a freshly updated Cuis image, installed with DrGeo code, in 
> developer set, I can execute this code now:
>
> *Smalltalk at: #LogStartupDebugAids put: true*
>
> When I save the image without quitting, the mouse cursor turns to the 
> writing cursor, image stalled, no output on the console from where was 
> started the VM
>

If I try to do the same in a bare Cuis, it works OK. I guess that 
whatever is creating problems also runs when you save the image.

> I also test with my bundle build procedure where I also turn on this 
> log startup flag. At the end the image is automatically saved and 
> quit. There is no issue.
>
> When the bundle is  started, DrGeo hangs, console reports:
>
> 2022-08-17T16:35:16.171 process:79 926479 To #openSourceFiles
> 2022-08-17T16:35:16.174 process:79 926479 To #initClassCachedState
> 2022-08-17T16:35:16.184 process:79 926479 To #doStartUp:
>
> When I run the image with the VM -tracestores option, I have more details:
>
> 2022-08-17T16:44:09.937 process:79 926479 To #openSourceFiles
> 2022-08-17T16:44:09.940 process:79 926479 To #initClassCachedState
> SmallFloat64>+
> SmallFloat64>+
> 2022-08-17T16:44:09.950 process:79 926479 To #doStartUp:
> Delay class(Behavior)>startUp:
> DisplayScreen class(Behavior)>startUp:
> Cursor class(Behavior)>startUp:
> InputSensor class(Behavior)>startUp:
> ProcessorScheduler class(Behavior)>startUp:
> WeakArray class(Behavior)>startUp:
> Locale class>startUp:
> NaturalLanguageTranslator class>startUp:
> DrGeoSystem class(Behavior)>startUp:
>

I'd dig deeper here: DrGeoSystem class>>#startUp:

> SmallFloat64>/
> SmallFloat64>>=
> SmallFloat64>-
> Point>+
> Point>+
> SmallFloat64>=
>
> All in all, -tracestores gives complementary information to your 
> changeset. But it is still too little information.
>

btw, I have no clue what -tracestores is about. Any docs?

> I have an issue in my startup sequence, I think there is a weakness 
> somewhere in the font handling. It is possible my startup sequence 
> execute unproperly with a wrong path name to font or/and a wrong font 
> name. I have observed Cuis does not like that kind of things.
>
> Oh, if I don't kill quickly the stalled image, it also eat up all the 
> 24 GB of my workstation, forcing me to hard reset it.
>

What happens if you postpone the setup / startup of DrGeo to until the 
GUI is ready? For example, instead of running stuff, throwing the 
Smalltalk expressions to the Transcript, and evaluating them by hand 
once the system has started. Maybe that helps?

> Thanks
>
> Hilaire
>
>

I think it is clear that there is some problem in the DrGeo startup 
sequence. By seeing senders of #logStartupDebugAid: you can see that you 
can do "Smalltalk logStartupDebugAid: myStuff" anywhere in your startup 
sequence to find what is the last thing that runs correctly. You can 
also dump any parameters or stuff that might help you understand the 
problem. This is traditional "debug with print statements".

Or, if you want, I can try to debug it myself. But I need a complete set 
of files and instructions to be able to do exactly what you are doing, 
and get exactly the same results. I'd need to do the build of DrGeo myself.

HTH,

-- 
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20220817/6078dd91/attachment.htm>