Who's Online |
62 user(s) are online ( 45 user(s) are browsing Forums)
Members: 2
Guests: 60
smf, rwo,
more...
|
|
|
|
Re: lowlevel.library problem??
|
Posted on: 2022/10/29 17:27
#101
|
Just can't stay away 
|
@thread
Is this still relevant?
|
|
|
|
Re: SpotLess debugger
|
Posted on: 2022/10/29 16:16
#102
|
Just can't stay away 
|
Here's the latest version : Spotless v.2.1.0@kas1e I am really hoping, that I have solved all of your present inquiries. If not, I will be happy to receive any new and relevant complaints :). To answer your question : I have not done an AmigaGuide, because I think the user should be able to figure out the gui without guidance. If this proves to be a problem, I will consider doing a guide (just like in the old days) for an upcoming version.
|
|
|
|
Re: SpotLess debugger
|
Posted on: 2022/10/28 17:12
#103
|
Just can't stay away 
|
@kas1e Quote: 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 ? Fixed. Quote: 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.
Fixed. Quote: -- Issue which i report back ago still there and with which we circles around for too long :( To reproduce:
This one is tricky. I am pretty certain, that what is happening is, that one of the variables or entries in the structs are uninitialized. There should be a safety on memory reads detecting, if an address is readable. But apparently it doesn't work. So the unreadable address is being read, which causes a crash. I am trying to consult the dev team for assistance. Quote: -- 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
As mentioned before : There is no stepinto for assembly functions in the main window, since there would be no code to show in the code box. If you want to step into assembly functions, you will have to do it from the lowlevel assembly debugger window (aka The Memory Surfer). Quote: -- After making a breackpoint and hittin "Start" and then click on "Memory Surfer": the Memory Surfer window is just empty.
I will fix this.
|
|
|
|
Re: SpotLess debugger
|
Posted on: 2022/10/27 15:21
#104
|
Just can't stay away 
|
New version out : Spotless v.2.0.2.@kas1e I have not done much work on it recently. But I have a few changes, that are in my local repository. I will commit them a little later. EDIT: Actually that was useful input. I did have a repository criss-cross, with multiple instances of the Spotless repo with different improvements to each. I have now deleted unnecessary copies and reduced to one. I am hoping, that all my well formed changes are intact.
Edited by alfkil on 2022/10/27 16:22:42 Edited by alfkil on 2022/10/27 16:23:14
|
|
|
|
Re: SpotLess debugger
|
Posted on: 2022/10/27 11:28
#105
|
Just can't stay away 
|
@kas1e
Actually, the problem with choosing cancel in the load requester seems to be not that simple. Apparently, the call to CreateNewProcTags returns a positive value, when just the folder is selected, and there seems to be no method to detect, if the load has actually failed. Could you maybe take a look at this?? This is in the SimpleDebug/Process.cpp file.
EDIT: Nevermind. It has been fixed.
|
|
|
|
Re: NovaBridge released!
|
Posted on: 2022/10/27 9:58
#106
|
Just can't stay away 
|
@kas1e That's fantastic news! We have been needing this. 
|
|
|
|
Re: SpotLess debugger
|
Posted on: 2022/10/25 11:06
#107
|
Just can't stay away 
|
@rjd324
In principle, you should be able to downgrade to Final Edition CD version and use Spotless on that. But yes, practically it is only supported for latest beta kernel and elf.library.
I will update the readme once I am ready with version 2.0.1.
|
|
|
|
Re: SpotLess debugger
|
Posted on: 2022/10/24 16:41
#108
|
Just can't stay away 
|
@kas1e
I am having my Amiga system back in a few days, and I will fix these two things.
Just to be clear : Normal functioning should work. That is, if you choose a file to debug and DON'T click cancel, it should actually load (provided it has been built with -gstabs), and you should be able to do at least a few successful moves around the code using steps. If it doesn't, then there must be something with the system updates.
|
|
|
|
Re: WebKit based browser initiative
|
Posted on: 2022/10/24 12:43
#109
|
Just can't stay away 
|
@Antique
I need hugs and cuddles. And maybe a little bit of cash. And people shouting out of sheer joy. But first of all I need to set myself up for the task. That's gonna take a little while.
|
|
|
|
Re: WebKit based browser initiative
|
Posted on: 2022/10/22 10:54
#110
|
Just can't stay away 
|
@kas1e Quote: 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. I actually did build webkit with a native compiler back in the days. And on a Sam440 too! It took the whole night, and I would sleep next to the machine to listen for drive noises. ;)
|
|
|
|
Re: WebKit based browser initiative
|
Posted on: 2022/10/21 16:51
#111
|
Just can't stay away 
|
Not necessarily relevant to the current thread. But I *did* already do a complete build of chromium for Qt6 with a cross compiler, and it didn't link correctly, and it was a mean bitch to work with. I do believe, it is within the realm of the theoretically possible getting it to work, but it is not very much fun doing the work, and I might decline doing anything further with it, unless there is some really serious motivation involved.
I think this thread is interesting with a more sensible goal orientation. I did do the Qt4 webkit module on a similar code base, so maybe I would have some knowledge to chip in. Hoping to see it developing further.
|
|
|
|
Re: Is QT 4 or 5 still alive somehow?
|
Posted on: 2022/10/17 17:01
#112
|
Just can't stay away 
|
@SinanSam460
I have left a comment for you in the issues pane in the Qt6 repository.
|
|
|
|
Re: Is QT 4 or 5 still alive somehow?
|
Posted on: 2022/10/17 9:40
#113
|
Just can't stay away 
|
@kas1e
Thanks! That is good to know. Just have to get my AmiSphere account up and running, I guess.
|
|
|
|
Re: Is QT 4 or 5 still alive somehow?
|
Posted on: 2022/10/16 11:18
#114
|
Just can't stay away 
|
@SinanSam460
I have not given up hope completely. The current work on Qt6 got stalled because of a bug in elf.library. I am trying to find out, if this has been fixed already.
I am also in a moving situation, so it will be another month, before I can resume work.
|
|
|
|
Re: SpotLess tests need it to find out one bug
|
Posted on: 2022/7/4 16:11
#115
|
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.
|
|
|
|
Re: SpotLess tests need it to find out one bug
|
Posted on: 2022/7/4 12:41
#116
|
Just can't stay away 
|
@rjd324
Yes. That's exactly what I am referring to.
|
|
|
|
Re: SpotLess tests need it to find out one bug
|
Posted on: 2022/7/3 13:53
#117
|
Just can't stay away 
|
@rjd324
Are you running pulic update 2? If so, then that is the reason.
|
|
|
|
Re: I get by with a little help from my friends (Odyssey)
|
Posted on: 2022/7/2 16:36
#118
|
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!
|
|
|
|
Re: SpotLess tests need it to find out one bug
|
Posted on: 2022/7/2 16:30
#119
|
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).
|
|
|
|
Re: I get by with a little help from my friends (Odyssey)
|
Posted on: 2022/7/2 6:17
#120
|
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
|
|
|
|