@Hans I ended-up using "-g" rather than "-gstabs" (as your blog suggests). Sadly I can't remember the reason now, nor what difference it is supposed to make.
@Hans Yep, that your article is nice, and add2line is welknown, its just i choice to avoid mambo with addr2line, as well as its easy for copy+paste/forwarding/etc crashlogs when they have names of functions insted of reference values, which i need manually translate and loose time for.
@ChrisH -gstabs just recommented by core devs on os4 (dunno why, maybe they have reasons for), but its about the same as -g. On linuxes -gstabs produce debug binaries without GDB extenstions, while -g produce debug binaries with GDB extensions. It can be that our old GDB do not handle any special GDB extensions, so for us its all the same, -g or -gstabs.
@Raziel When i see something swapped around (like mirrored on your image), i always think about endianes differences. But i can be wrong. Its always good to compare morphos version on the same sites if anyone have ability to do so, so to known if it non os4 port specific problem
Browsing to this site makes part of the text display mirrored.
I (seldomly) stumble over such sites, why is that? Is Odyssey interpreting css/html code wrong?
I'd say its a feature of the website. Try clicking on either of the cards, and it will flip to display the text correctly.
Glancing at the HTML code, there's indications that this flip-thing is disabled in certain browsers (probably those that doesn't support the attribute "flip").
I just talked to a MorphOS User about my router problem and (as he has nearly the same setup as me) he is still able to access his router (with the same firmware) but he's using Odyssey 1.24//MorphOS.
He also tried it with Sputnik and gets the same error message.
So, would it be possible to update our port to 1.24, please? I'd really like to be able to access my router again.
I just talked to a MorphOS User about my router problem and (as he has nearly the same setup as me) he is still able to access his router (with the same firmware) but he's using Odyssey 1.24//MorphOS.
He also tried it with Sputnik and gets the same error message.
You may ask him to try 1.23 morphos version.
If it will not works on 1.23, but work on 1.24 => webkit problem. If it will works on 1.23 on mos, then or porting-to-aos4-problem, or something with settings.
Quote:
So, would it be possible to update our port to 1.24, please?
I didn't see sources of 1.24 online, but newer ones (which on github), and which, have welknown js-endian problems.
If this project is successfully funded, and as long as the resulting ports stay true to the original version of the Odyssey Web Browser in terms of user experience and feature sets, Fabien Coeurjoly plans to share all source code that he will develop himself for future versions of Odyssey Web Browser for free.
I therefore assumed that OS4 being stuck on Odyssey 1.23 was due to our developers (esp. you) being rather busy...
I thought Fab was going to release the source code of all future versions of Odyssey
He release 1.25 version, which is last one, on github, which have endian issues, because of which he didn't release 1.25 for morphos, and because of which we don't have it on os4 as well.
Quote:
I therefore assumed that OS4 being stuck on Odyssey 1.23 was due to our developers (esp. you) being rather busy...
Probably you wasn't involved in those discussions everywhere in last year, but new version of webkit have problems with endianes in JS related code. Until they not fixed, webkit will crash on big endian machines almost on every modern site. There and on amigaworld, and on morphzone few threads about, to summorize which: everyone hope that someone (like Fab) will deal with it :)
@ChrisH Probably he just skip 1.24 and put latest code which he have on github in hope that someone else will help with those ppc problems too. But i got what you mean :)
I just talked to a MorphOS User about my router problem and (as he has nearly the same setup as me) he is still able to access his router (with the same firmware) but he's using Odyssey 1.24//MorphOS.
He also tried it with Sputnik and gets the same error message.
You may ask him to try 1.23 morphos version.
If it will not works on 1.23, but work on 1.24 => webkit problem. If it will works on 1.23 on mos, then or porting-to-aos4-problem, or something with settings.
Just now got the reply from him and he's also not able to log in (getting the error screen) with MorphOS OWB 1.23.
So it's definitely an update to the code i need.
Anything new regarding a possible 1.24/1.25 update for AmigaOS4?
Anything new regarding a possible 1.24/1.25 update for AmigaOS4?
I thinking about making 1.24 port as well (through i didn't see sources of that version), but there (in 1.23) so many aos4 specific changes already, that making same for 1.24, and then for 1.25 pretty time consuming. From another hand, 1.25 still have those big-endian issuess and as far as i know, MacOS/ppc versions of latest webkit still crashes, so no one still fix them properly (what meant till that not done, there no big needs in compiling 1.25 version).
I do not know what we can do for now. Deadwood says that probably it can be better to make aos4 version of 1.25, even if it will crashes all the time and will be unusable and be in hope that someone will someday fix webkit for big-endianes, and then we can update code. But then, it can be never done, so (imho) better to wait when webkit will be fixed (for macos, or morphos or whatever), and then.
I thinking about making 1.24 port as well ... but there (in 1.23) so many aos4 specific changes already, that making same for 1.24 ... pretty time consuming.
I don't know the code, but I wonder if it is possible to rewrite the 1.23 changes for OS4, such that they are mostly (new includes containing) #defines that modify procedure calls (to be OS4 friendly)? Then it would be easier to reuse such changes for 1.24/1.25.
Just a few days ago, i was able to use Odyssey both when signing in to DNB (Norwegian bank using bank-id through a small authenticator) and when logging in to NAV and Digipost (also uses the same authentication)
Now i get javascript and cookie error. The js error is something "deflected.xss" and the cookie and auth ssl key is for another domain. Also when opening the cookies window in Odyssey, and search for the cookie, ALL the cookies under that domain three says they expire 1. jan 01:59.:59 1970
A friend of mine, very into Linux and Debian, responded very sceptic to the .xss warning, saying he would have turned off the computer and not entered any more passwords or personal information.
Anyways...
Odyssey worked both in DNB, NAV and Digipost WITH bankid (electronic authenticator) before i upgraded to 1.23r4, BUT... NOW it works with youtube and google services...
Weird
(NAV = www.nav.no - An governmental site for unemployment. there's a login button at top right, which opens a window to different authentication options. the "BankID" one is number two. fails with a timeout)
(DNB = dnb.no - an online bank. There's a field on top right where you can enter a birthdate which opens the same auth window as NAV and times out with same error).
@Shamron I tried your NAV link and I get all the way to the point where it has and input box for a User ID. It did take about 10 seconds to find a bank ID before I got there and I don't know where it got a bank ID for me.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
I use it on AmigaOS 4.1 Update 6.
