Latest version. Generally stable. However loading imgur now causes GR. Imgur used to work ok? I have made no changes to odyssey or MUI.
Crash log for task "OWB" Generated by GrimReaper 53.16 Crash occured in module OWB at address 0x7F160E6C Type of crash: DSI (Data Storage Interrupt) exception
@ddni Please, remove everything after "Expansion buses", it not need it , but make reading of thread harder.
As for crash itself, some sites may crash, make bug-reports on bugs.os4depot.net / odyssey.
EDIT: in case with inmgur.com site , its also crashes on 1.17 version of morphos version of odyssey, but works with 1.23, what mean, that once 1.23 for os4 will be released, that crash will gone (as many others with such stack trace).
In meantime you can do what kicko do : in url preferences disable java for sites which crash you.
@Thore From all my tests with 1.9 / 1.16 and now 1.23, i can say that all reports about sites crashes with such stack traces / disassemble / registers info its all webkit bugs, which they fix later. For example big bunch of crashing sites on 1.9, start to works on 1.16 (while some still crashes). And for sake of tests i do test morphos version as well, and the same sites the same crashes on the same versions, and stop crashes on recent ones.
@tlosm I mean 1.23 on morphos, aos4 version still in process: currently i only port latest libcairo, libpixman, ffmpeg, sqlite, core of mediaplayer (with help from Daniel), compile odysseys's libjsc.a, libwtf.a and almost compile libwebcore.a (which is huge and big, and which have some moments to fix which wasn't need it in previous versions) , and once it all will be done, then there will be need to compile all that mui-amiga-native-code, which for sure will have something to fix for os4, something to rewrite which wasn't in previous version, as well as new class for autoform-filling is need it (calltips.mcc, but i hope Thore as usual will deal with it). After all will be compiles there for sure will be some linking problems after fix of which it will crashes on running for sure, then those fixes, then it will works but mediaplayer will be crashing for sure, also fixes and so on.
I.e. in progress, but slow notebook with cygwin take time for compiling as well as i not sit whole days over it too :)
Also will be good if someone will re-implement spellchecker.library , which is also in use by odyssey.
Yes, because all those parts was mostly ./configure; make with some very minor changes. All the other stuff going mostly like it was for previous versions, except mediaplayer and some new small problems related to compiler
The value 0xcccccccc in r9 clearly points out a duplicate Remove() of a node from an Exec list.
Not really. I use memory allocators that also clear deallocated memory with this pattern. So it could be a double deletion in WebKit objects, most likely.
If you have an sqlite3 later than 3.7.5, can you please upload it to OS4Depot (when it's ready) along with source? Assuming it has an updated os_amiga.c. I have 3.7.5, but there are reasons I won't stick it on OS4Depot. I put the source on SpotUP's server (used for SdkServer. Go there manually via HTTP).
-DSQLITE_OMIT_WAL=1 need it for disable sys/mman.h dependence with all those MAP_SHARED, PROT_READ, etc.
--disable-dynamic-extensions need it for avoid using dynamic externsions (dlsym, dlclose, dlerror calls, etc)
I also have 3.7.5 version from HansJoerg which he use for TW, but currently i stick with my own to see if it will works at all, and if there will be any bugs (so if yes, then will reuse Hans's one).
Oh ok. I was under the impression that sqlite didn't work at all without the specific Amiga filesystem code (like trying to port findutils. If someone can do that, that'd be great). If in the future I port something that needs a later sqlite, then it's good to know I can just do a straight port.
0xcccccccc?? but how do you know, that this memory is never going to be allocated?
As I see it your creating potential problems, there most be better ways to deal whit duplicate Remove(), way not log the error some where else?
If the memory is reallocated it should be reinitialised, thus no problem, if not this munging forces a "safe crash" and the developer can fix the code.
In the case of the list node, you *must not* rely on the ln_Pred and ln_Succ pointers being valid after the node is reomved, so there is no issue.
@ddni Yep, it works on 1.23 aos4 port. Also notice that there was some ad-video block with video and speech : works too now ! I for first even didn't get what happens, some woman from that ad start to talk bull and i didn't realize at first that it from odyssey :)
Excellent! Thanks. Great to hear of progress which I understand! The "libcurl etc etc" type discussions on the "official" Odyssey 1.23 thread go waaaay over my head.
From a users point of view, how close to a beta release are you?