@AlexC

Quote:

So the code tried to jump to an instruction at address 0. Unlike a DSI which usually happen with wrong or uniitialized pointers, this can be caused by a number of things.

Yeah, but we already know that with even default debug level, i mean in crash we have:

Quote:

Trap type: ISI exception Machine State (raw): 0x1200F030 Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on] Instruction pointer: 0x00000000 Crashed process: owb (0x66893AF0)

And there is already says that Instruction pointer: 0x00000000 .. I also found at end of crash that (in debug11):

Quote:

[HAL_Alert] ALERT! 0x80000003 [HAL_SuspendTaskWithUpdate] Suspending 0x66853DC0 with state 2, DAR = 0x00000004, at IP = 0x00000000, LR = 0x7FFF690C [HAL_SuspendTaskWithUpdate] Adding to suspend list [HAL_SuspendTaskWithUpdate] Context @ 0xEFDC9BA0

As far as i remember, that ALERT! 0x80000003 mean null-pointer access as well (but its also say not so much for me).

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@kas1e

Crossing my fingers for you squashing those bugs.

_________________
I'm an antique. Don't light my fuse

@kas1e

If a library was not opened, you will get a ISI error.
If a plugin does not work you will get a ISI error.
If you have function pointer set to no value or NULL you get a ISI error.
If a MUI class is not loaded.

There are two option library a application depends on does not load, or the memory is corrupted.

Also look for pointers like

void (*my_func) (void *ptr) = NULL;

_________________
Software developer and forum troll.
Please check out my software:
Excalibur, Basilisk 2, AmigaInputAnywhere.

@NutsAboutAmiga

In my opinion, the most obvious candidate in this case is a method called from a null or disposed c++ object, and there could be many reasons for that (even possibly webkit bugs).

Here, the real problem is we don't get any usable stack trace in this case. The fact this exception also takes down OS4 with it is also weird (unless it happens in a critical kernel module).

On MorphOS, I often stumbled on this kind of illegal instruction from 0x0/0xwhatever address, when porting or merging webkit, but at least, only OWB dies in this case, and i get a well readable stack trace telling me where it happened.

Last edited by Fab on 06-Mar-2011 at 12:48 AM.

@Fab

Well maybe it has some thing to do whit .so objects.

You normally get a error unless is loaded it dynamically whit dlopen().

Last edited by NutsAboutAmiga on 06-Mar-2011 at 02:37 AM.

_________________
Software developer and forum troll.
Please check out my software:
Excalibur, Basilisk 2, AmigaInputAnywhere.

@NutsAboutAmiga

Quote:

If a library was not opened, you will get a ISI error. If a plugin does not work you will get a ISI error. If you have function pointer set to no value or NULL you get a ISI error. If a MUI class is not loaded.

Its all sounds logical as well, but in this case you still have stack-trace, which point you on problem. )

Quote:

Also look for pointers like void (*my_func) (void *ptr) = NULL;

Its not that easy. There is thousands functions, and which one are ####s and where - crashlog not say at all. No stack trace, nothing.


Quote:

Well maybe it has some thing to do whit .so objects. You normally get a error unless is loaded it dynamically whit dlopen().

We not use any .so there, and everything static.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

Removed and opened a new thread.

Last edited by Mrodfr on 06-Mar-2011 at 06:52 PM.
Last edited by Mrodfr on 06-Mar-2011 at 06:13 PM.

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mrodfr
If you doent mind, plz start new thread about (its a bit too much questions which will scare devels which will in interest to help us with our lockup-problem). But in other topic, for sure someone will explain you all the stuff more.

Last edited by kas1e on 06-Mar-2011 at 06:39 PM.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@kas1e

Been a couple of weeks, just wondered if there had been any progress?

Cheers.

_________________
If your nose runs and your feet smell, you're upside down.

@TiredofLife

In last time we was in slow mode about it, but yesterday we with Deniil start again, so the plans for now are: fix few little bugs which we have for now, and then, if our hardcore bug still will be present (that one which cause random freezes after a while), then fight with it.

Anyway why we a bit chill for now : because update3 will be minimum (because new mui will have many bug fixes, and update3 will 100% necessary for (or mui from update3). And while as i see it will be released dunno when, we can be not so fast (expectually now, when we have just few little bugs, and one hardcore one).

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@TiredofLife

I've had some personal issues, a ski trip and a broken car that I've been busy with the last few weeks. But as kas1e says, since update3 is needed there is no huge rush anyway.

_________________
>Amiga Classic and OS4 developer for OnyxSoft.
>A1-XE/G4, Radeon9250, Sweex 5.1, SII680
-Don't hesitate to contact me about my programs, but please use e-mail instead of PM. E-mails are more likely to be read in time, and easier for me to keep track of.

@kas1e

Quote:

Anyway why we a bit chill for now : because update3 will be minimum (because new mui will have many bug fixes, and update3 will 100% necessary for (or mui from update3). And while as i see it will be released dunno when, we can be not so fast (expectually now, when we have just few little bugs, and one hardcore one).

Unless it turns out that random freeze bug requires a fix in another OS/MUI component in which case it would be bad if Update 3 was released before you find that bug since then it couldn't include the necessary fix and then you'd have to wait for Update 4 to come out

@COBRA
Quote:

Unless it turns out that random freeze bug requires a fix in another OS/MUI component in which case it would be bad if Update 3 was released before you find that bug since then it couldn't include the necessary fix and then you'd have to wait for Update 4 to come out

:) Right :)

Because of that i in hope that we of course will finish all before update3 will be out (to avoid that problems). Imho in next days / week we will fix all the small bugs and will concetrate on heavy one.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@kas1e @Denill

Cheers lads.

_________________
If your nose runs and your feet smell, you're upside down.

@all
Some summ-info about mui-owb port:

There is what need to fix (all the other mention before on other pages bugs are fixed):

1. BitmapImages by some reassons not works when we use List (maybe we use it wrong in terms of mui3.9, need to investigate), and because of its we not have :

- favicons in history-panel and history-of-urls
- gauge in download manager.

Need to invistigate, and make workorounds in code, or add stuff to our List (depens what will be easy way).

2. Context menu by RMB mostly works everythere, but at one-two windowse not (very small bug, and windowses are not so important, but still, to make all perfect need to fix).

3. need to fix "curl library port". I build latest version few days ago without threading/tls and all the wrong stuff, but still, need to do some manual work, to make "file://" protocol works with amiga pathes, which will fixes local usage of files, drag and drop of local file to OWB and related stuff.

4. "About" window show nothing (use mui4 about class, need a bit rewrite). Easy, but should be done as well.

5. Iconify not works (i.e. works, but wrong, need to fix). Should be easy as well, but still need to fix.

6. Some crash in some place on bubble-helps. Not big deal of course, can be disabled at all, but, for sure better to found why and which (better and for our mui, and for port at all).

7. Some random lockups - the heavy problem and the most important problem about which we talk on last 5 pages here: we will leave it to the final end, when all the other will works and only that will be last bug to fix (just to avoid any problems related to "because of that bugs which we not fix before, we have also side-effect bug which unpossible to fix before main one not fixed").

All the other works fine (well, at least as i can see, for sure somethere something still here, but visually only what i describe now are need to fix).

Last edited by kas1e on 22-Mar-2011 at 12:37 PM.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@kas1e
Thanks for the update.

Awww bubble-help, I remember them from 'back in the day'. I wonder why Apple never nicked that one lol

A square tooltip vs a bubble tooltip... who will win? Only one way to find out...

FIGHT!!!

_________________
Official AmigaOS Website
AmigaOS on Facebook
Lake Marketing and Events

@kas1e

Thank's foe the update ang GOOD WORK!

_________________
Simone"Tuxedo"Monsignori, Perugia, ITALY.

@all
mui-owb progress:

- iconify works now
- for "About" bug works on new class is starts
- and Deniil almost found why we have problems with images in urlhisotry/gauge

Last edited by kas1e on 24-Mar-2011 at 12:08 PM.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@kas1e

Very good, so points 4 and 5 are closed now

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6