Error reading prefs file from disk config.prefs. A new file will be created.".

So the problem is in the c++ copy operations mixing vectors and lists ?

PS. Maybe it worth to try to build spotless with latest afxgroup's clib2 ? Just to see, if issues with copy will be there ?

Hm, i just tried to run db101 alone, without Spotless, and it runs ok, without crashes. But when i run it inside of spotless (with removed pipe) it still crash.

I am sure kernel guys will fix it, if we will provide them with minimalistic test case. This one also will help for us to see if issue actually a kernel, on on our side. Because if we will say them "spotless on exit bring issue about Disable!", they will ask for minimal test case, as they will not dig in into spotless to find if it fault of app or of a kernel.

Imho, as in the other case we need to provide a minimalistic test case showing the problem, then it have chances to be fixed. Because if we will say that "CloseElfTags() broken", they will for sure fix nothing :)

I am thinking firstly about garbled output in variable yes, and then, also non-working stack trace.

Are you sure about ? I mean, i didn't see any other amigaos application which when do copy freeze the whole OS and take so much time for copy.

Sounds bad yeah if we can't put instead of trash something like empty spaces or word "none"..

Everything fucked up with strange bugs :) and we don't know what/where/why

And to say truth i didn't understand stuff about pipe :) Is it issues inside of spotless, or did you say that if programm with reference to pipe is loaded, then it will not works ? I just didn't understand part about needs to change anything in db101 : db101 works fine as before, and if i remember right i can load db101 inside of db101: it's spotless which bring us such issues for now and which we tried to fix. Or i just dumb enough and not understand all that stuff about pipe ?:)

Through then big question : why it works for you before when you test the same version as me ? :)

Ok, let forget Spotless. Take an db101 from os4depot, it have -gstabs inside. Then load it inside of spotless : the same freeze ! But it just 1megabyte binary ! And you can't the same run it !

I made a video to show the problem:

https://youtu.be/iwc5LnNyIBo

if i start spotless from the shell, load up test binary, hit breakpoint, hit start, hit again start to finish it up, and then close the spotless, i have in the shell:

***Command 'spotless' returned with hanging Disable!

- Uniconify generate a debug output, maybe need to be removed

- In about window there is a glitch in the copyright symbol

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).