Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
68 user(s) are online (38 user(s) are browsing Forums)

Members: 0
Guests: 68

more...

Headlines

Forum Index


Board index » All Posts (alfkil)




Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@rjd324

Ok, cool. That was all I needed to know.

Apparently the software (Spotless) works on some setups pretty much perfectly (your X1000 setup and my X5000 setup). Now, there are a lot of different versions of system components out there, so the short version of the story is, that we have working performance on some combination of system components and faulty performance on others.

The long version would be a lengthy explanation of why the different combinations work or not. This story is of course hard to write, especially when I as the only active developer only have access to an already functioning setup. In your case I can only comment, that Spotless was known to not function properly on public update 2. Whether or not the functioning on your X5000 setup would be fixed by updating to available beta software in the kernel and other places would only be found out by actually updating.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@rjd324

Yes. That's exactly what I am referring to.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@rjd324

Are you running pulic update 2? If so, then that is the reason.

Go to top


Re: I get by with a little help from my friends (Odyssey)
Just can't stay away
Just can't stay away


@alfkil

If I unpack Odyssey to a folder to RAM: and run here twice (one for indexing, one for testing), the problem is solved. Now I can copy the folder to the work: drive, and the problem - voila!

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@rjd324

Since you are using SimpleDebug, I am guessing, that you are using the version of Spotless available at os4depot. This version is obsolete and should probably be removed (please remind me). There are some links to newer executables in this thread, that all lead to the same file location at google drive. These are beta versions but are definitely better for testing at this point than the old version.

Anyways, the problem you mention with having a crash on the X5000 and not on the X1000 is very strange. I am guessing, that it has to do with the standard library version or some other component in that category, since your stacktrace shows a crash at just a std::vector constructor (so, there is a bug, but it only generates a crash on one platform due to other software on the machine).

Go to top


Re: I get by with a little help from my friends (Odyssey)
Just can't stay away
Just can't stay away


Doesn't work for me. :(

EDIT: The Conf/font directory is empty after running OdysseyLauncher.

EDIT: I think it is an issue with long file names. The cache files have quite long names, and I just realized, that I forgot to check 'Long filenames' when I formated my drives.

EDIT: Nope. That didn't solve it either. :(


Edited by alfkil on 2022/7/2 6:45:43
Edited by alfkil on 2022/7/2 7:19:20
Edited by alfkil on 2022/7/2 7:49:05
Go to top


I get by with a little help from my friends (Odyssey)
Just can't stay away
Just can't stay away


Hi guys,

What is the trick to killing the font indexing requester at startup in Odyssey?? I remember remembering it in the past, but I don't remember it anymore. Hielp!

- Alfkil

Go to top


Re: Qt 6 progress
Just can't stay away
Just can't stay away


@trgswe

I know all this. I have most of the modules, you are mentioning, in ready-built versions on my linux hd. I was able to build qt-creator, which needs the Qt5-compat library, so I am pretty sure, that everything I did has been set up correctly. The only problem, in fact, seems to be the link error I have been talking about and just a few other things, for instance qmake doesn't work natively yet.

If we could fix the link error, I would be able to proceed.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@LiveForIt

Quote:
There are no why the OS developers can solve this anyway.


There is no automatic ressource handling. In principle you can call RemTask(processHandle), but any files or windows opened will be left astray. I think it is a sensible preference, since the overhead of tracking every ressource is massive.

EDIT: I am going to change it, so there will be a popup warning before closing on the orphan.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


I am up and running again.

I have flawless performance from Spotless in the described tests with kernel 54.46.

I have fixed the float register writeout to look a little nicer.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

I think it best, that I postpone further development until I have a working machine back. It could take a couple of weeks, but then I could end the 'shooting-in-blind' frenzy, that I am in currently.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

I am not sure, if it is a bug or more like a missing feature. Also, it is more like a guess than an actual solution. But afaik there is currently work being done on features, that have an impact on the exec debug functions.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@thread

There is a possible problem with later machines (including x5000) and the debug interface of exec.library. I am quite convinced, that the current state of the software is the 'correct' one, but there is a system component, that needs implementation, before it can be used with later kernel releases. This, at least, is how the explanation goes so far.

So I guess patience.


Edited by alfkil on 2022/5/31 15:16:33
Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

Just for a thought : Can you try, after Spotless locks up, if you can exit by CTRL+C from the terminal.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

Quote:
Nope.. I run load test case, hit bp on puts(), click start, once it drops i hit "step out" , then nothing in console, test case from gui of spotless looks like finished and GUI not operational anymore.


But it worked previously?? This seems overly random. I am not sure, I am very motivated to solve these issues. Maybe it is just impossible to get this software to work.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

Quote:
Btw, I also do test what Javier found, and yeah, the same for me. You enough to just load test case, run it (even without hittting any breakpoint), and then one it bring hello in console and exit, just hit close gadget. And you see in the shell that:
***Command 'Spotless' returned with hanging Disable!

But (!) i should add that this happens on the latest beta of kernel. On the previous betas of kernels and on latest public version we do not have such stuff. So chances are high that this is kernel itself and you can skip it for now. I report it to os4beta


This, as explained earlier, is because you cannot safely close Spotless with an existing child. This is a system feature, and the only thing I could do, would be to prevent closing when the child is still in memory. Do you really want that??

EDIT: I have re-read what you wrote, and yes, this seems to be a problem with the new kernel. I don't know how to solve it.
Quote:
But now i tested more, and "Step Over" also buggy seems so. You need working machine for sure, or we will jump on the same bugs again and again without much progress :) Just load up a test case , then hit bp on puts() , and hit step over few times , you will have non working gui of spotless.


Try this : Spotless_getPhysicalAddress


Edited by alfkil on 2022/5/22 11:15:36
Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

Try this : Spotless_stepOut(1)


Edited by alfkil on 2022/5/21 17:54:11
Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@kas1e

Thanks for report! This is a bit more complicated than expected. I need to think about it for a little while.

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@thread

*BUMP* ( stepOut() )

Go to top


Re: SpotLess tests need it to find out one bug
Just can't stay away
Just can't stay away


@alfkil

This should fix the long long int printf :

result.push_back(printStringFormat("%lld\n", (uint64_t)context->fpscr));


New download : Spotless _fix_longlongint

@kas1e

Please look at the previous post also.


Edited by alfkil on 2022/5/21 11:51:16
Go to top



TopTop
(1) 2 3 4 ... 69 »




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project