At least will be good to have no garbage in variable, or maybe dunno, somehting like "unimplemented" words ?:) I just fear while there garbage, it mean trashing of memory.

First one:

-- run spotless
-- hit rmb, choiise "Swith to public screen".
-- hit iconify gadget. It will iconify to the WB screen
-- swith by any way to workbenh screen (drag the spotless screen down, or hit gadget on spotless screen to back to the wb one)
-- hit on spotless window => crash.

Crash in Widget.cpp:165

I think that crash i have once on exit was related to that public-screen functionality as well. Maybe that just one single issue.

-- when you iconify, the icon on the wb not of spotless, but default one. If i remember right it's about just additional option provide when do iconify.

-- when we tried to load Spotless binary inside of the Spotless, then progress bar going on fast (but while it happens, mouse is sluggish, 100% cpu loading). Then, everthing just stops/halts, and only after a few seconds (3-4) it refreshes and things show ups in Spotless. Imho if we can't speed things up for now there, will be worth to show progress bar finished only when evertyhing visibly on screen. Or, at least after progress bar finished, shoup a "busy mouse cursor" so we know it not freeze (but at this point, you can't move anything, it just like freeze, strange..).

Then after all loads, i hit the start and spotless didn't starts inside of spotles. Tried few times. When exit from main spotless, intuition seems to be messed up and trashed (so reboot need it).

Through i have one suggestion for : rename "configure" item to something like "add additional source directories" or something of that sort, so GUI will be self-explained.

Another suggestion for GUI, is to open "memory surfer" a bit bigger. Now it just as small as possible, but imho worth to open it by default so to be as big as it needs to fit whole horizontal information. Or do it like in some of our projects : gadge on bottom right together with iconify, where we can choose snapshot/unspanshot .. But maybe that will for now overcomplicate the things, and maybe just open it a little bit bigger will be fine for now.

-- when you switch public screen (so to have spotless on it's own screen), and load a some test in it, then it it runs on workbench screen, and not on the Spotless one. I.e. if we have in test case printf("aaaaa\n"); then when we on the spotless screen, this "aaaa" window opens on the workbench screen. While, imho, should be on spotless screen (as this is the default screen now, when we swith to it).

Another issue which i see right now, is that once i set breakpoint, hit start, and switch to variables, then while it works, it give me some garbage of 4 bytes under each entry in myTT: and in dup_prot_seletor doo. I.e. parts with values or addressses (like missing null termination or so).

Next issue the same when i hit breakpoint and hit start : swith to stacktrace : none. But this functionality surely works (in the profiler tool author get it correctly for sure).

1. a bit broken packaging of archive:

-- Directory inside of archive named "Spotless_drawer", dunno for what.
-- It didn't have directory "sobjs" with libstdc++.so anymore, is it expected ?

2. bugs:

-- RMB didn't works. I.e. menu spawns, but nothing can be called from, not ABOUT, not Configure, not Switching to public screen, nothing. Once you choose anything, it simple closes and nothing happens.

-- all entries in RMB menu marked with letter "A" the same for everything, like, "A" key for any entry.

-- Issue which i report back ago still there and with which we circles around for too long :( To reproduce:

-- And another issue: seems StepInto now works just the same as Step Over. I.e. i can't step-in into prinfs() for example anymore

-- After making a breackpoint and hittin "Start" and then click on "Memory Surfer": the Memory Surfer window is just empty.

Even with 10 years old WebKit (which we use in latest version of Odyssey), it was already about 5 hours to compile whole webkit on fast and modern PC with cross-compiler, and the only times when we use native compiling was when Daniel from onyxsoft helping me with rewritting morphos's parts to amigaos4's analogs. He have only x1000 at this time, and then i created for him manualy makefiles to build only libwebkit-owb.a (which was only amigaos native GUI code), and then giving him those parts from webkit itself like libwtf.a, libjsc.a and libwebcore.a, and he link them together with libwebkit-owb.a he compile on x1000. libwebkit-owb.a was just about 3megabytes of size.