@Maijestro

There is definitely a wrong calculation of inner width, inner height, I expect break on AmigaOS3.2 if he had used a bigger window title font.

@Georg

I think that depends on internal handling of messages in AmigaOS4.x as well, if its safe or if it’s not.
not just if supports atomic or not.

Perhaps that’s something that should have a setter function, I was looking for function to set it, the other day, as know about ModifyIDCMP() function.

there is a queue of message some that might not have been yet processed, and some might be added to queue while the messages are processed. What happens to the messages in queue, waiting to be processed? After FLAG was modified. As they lost too?

@328gts

ExecSG team works for Trever. but ExecSG is part of AmigaOS4.1

@Georg

I think your just bring up this problem, because someone pointed it out at some point, do you have any actual example of anything that breaking because of this?

Quote:

it should run just fine. Portable C/C++ code compiled for 680x0 programs written in C/C++ will depend on shampooers or forbid / permit, to make struct or data atomic.

Only stuff optimized with assembler you can have problems with atomic instructions. atomic Instructions do not work on a data structure only one address at the time.

I was curious about example of atomic opcodes, so found a example for PowerPC.
https://www.mulle-kybernetik.com/artik ... zation/opti-4-atomic.html

I guess it can be useful if you keeping record of number of items in list or something, but this instructions won’t be useful for protecting a linked list for example, where you need to maintain a previous and a next pointer.

@joerg

Perhaps because some demos and program check what CPU you have, and refuse to start if you do not have 040 or 060 CPU.

@LiveForIt

needed to add -athread=native at end of the linking stage.

Thanks to rjd324

@LiveForIt

adding -lpthread did not help
SDK version is 54.16 (22.08.2022)

g++ -c -D__USE_INLINE__ -I./ -I../ vector.cpp -o vector.o
g++ -c -D__USE_INLINE__ -I./ -I../ pointer.cpp -o pointer.o
g++ -c -D__USE_INLINE__ -I./ -I../ undo.cpp -o undo.o
g++ -c -D__USE_INLINE__ -I./ -I../ iconify.cpp -o iconify.o
g++ init.o tools/rnd.o tools/plot.o tools/draw.o tools/line.o tools/curv.o tools/box.o tools/bar.o tools/circle.o tools/ellipse.o tools/cut.o tools/paste.o tools/symmetri.o tools/filledcircle.o tools/fill.o toolbox.o pen.o main.o vector.o pointer.o undo.o iconify.o -o ldpaint
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `__gnu_cxx::__mutex::lock()':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:150: undefined reference to `__gthread_active_p'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `__gnu_cxx::__mutex::unlock()':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:161: undefined reference to `__gthread_active_p'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `free':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:152: undefined reference to `__gthread_mutex_lock'
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:163: undefined reference to `__gthread_mutex_unlock'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `__gnu_cxx::__mutex::lock()':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:150: undefined reference to `__gthread_active_p'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `__gnu_cxx::__mutex::unlock()':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:161: undefined reference to `__gthread_active_p'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `allocate':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:152: undefined reference to `__gthread_mutex_lock'
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:163: undefined reference to `__gthread_mutex_unlock'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `_GLOBAL__sub_I_eh_alloc.cc':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:134: undefined reference to `__gthread_active_p'
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:135: undefined reference to `__gthread_mutex_init'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `_ZN9__gnu_cxx7__mutexD4Ev':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:142: undefined reference to `__gthread_active_p'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_alloc.o): In function `_GLOBAL__sub_D_eh_alloc.cc':
/opt/adtools/native-build/gcc-native-build-8.4.0/ppc-amigaos/libstdc++-v3/include/ext/concurrence.h:143: undefined reference to `__gthread_mutex_destroy'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_globals.o): In function `__cxa_get_globals_fast':
/opt/adtools/gcc/repo/libstdc++-v3/libsupc++/eh_globals.cc:116: undefined reference to `__gthread_getspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_globals.o): In function `__cxa_get_globals':
/opt/adtools/gcc/repo/libstdc++-v3/libsupc++/eh_globals.cc:128: undefined reference to `__gthread_getspecific'
/opt/adtools/gcc/repo/libstdc++-v3/libsupc++/eh_globals.cc:132: undefined reference to `__gthread_setspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_globals.o): In function `_GLOBAL__sub_I_eh_globals.cc':
/opt/adtools/gcc/repo/libstdc++-v3/libsupc++/eh_globals.cc:97: undefined reference to `__gthread_active_p'
/opt/adtools/gcc/repo/libstdc++-v3/libsupc++/eh_globals.cc:98: undefined reference to `__gthread_key_create'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libstdc++.a(eh_globals.o): In function `_GLOBAL__sub_D_eh_globals.cc':
/opt/adtools/gcc/repo/libstdc++-v3/libsupc++/eh_globals.cc:104: undefined reference to `__gthread_key_delete'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `fc_key_init_once':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:114: undefined reference to `__gthread_once'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `fc_key_init':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:107: undefined reference to `__gthread_key_create'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `uw_install_context':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:160: undefined reference to `__gthread_setspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_ForcedUnwind_Phase2':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:160: undefined reference to `__gthread_setspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_SjLj_Register':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:128: undefined reference to `__gthread_getspecific'
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:129: undefined reference to `__gthread_setspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_SjLj_Unregister':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:160: undefined reference to `__gthread_setspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_SjLj_RaiseException':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:147: undefined reference to `__gthread_getspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_SjLj_ForcedUnwind':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:147: undefined reference to `__gthread_getspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_SjLj_Resume':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:147: undefined reference to `__gthread_getspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_SjLj_Resume_or_Rethrow':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:147: undefined reference to `__gthread_getspecific'
/GCC/lib/gcc/ppc-amigaos/8.4.0/newlib/lib/libgcc_eh.a(unwind-sjlj.o): In function `_Unwind_Backtrace':
/opt/adtools/gcc/repo/libgcc/unwind-sjlj.c:147: undefined reference to `__gthread_getspecific'
make: *** [all] Error 1
6.Work:pro_2023/ldpaint>

@FirstNinja

I never seen Ian post here (nor am I sure what nick he uses), Ian ported it to AROS, kept improving it after I lost interest.

If he did post here, I let him answer as he is more up to date on the subject.

I don’t own a SID chip myself, so there was no incentive to support it.

@jap

Perhaps there is a difference between MK3 and MK4 driver, perhaps catweaselsid.device is for MK3 card/driver, the MK3 driver was written by some one else.

The source code for Linux driver was on CD I remember, I might asked for code, and burnt it myself, but I'm pretty sure it was in the package.

@jap

My driver did not support sid,
but what Ian added or not, I'm not sure.


Can be idea to have a std sid api or something, maybe there is sid library or something.

Perhaps if the Linux sources includes it, then OS4.1 driver can be updated to support it. But not a simple job, the OS4.1 api is different from Linux api, it will need to re-written it’s not a simple recompile.

@Gregor

yes, its 68K program, maybe on aminet, or fish disks

@Gregor

Have you treid filemaster?

@McFly

F11 for fullscreen is typical as well
As well as Window+F, or ALT+F.

@amiganuts

If you start program X, and run it, and quit program X, and run program Y, and Y crashes.
But every time you reboot and run program Y first it works, and it never crashes.

Then you can be look at an problem where variables are not initialized, or memory is not cleared,
in C you are suppose to set pointers before use, and initialize the memory before use, if need to.
obviously setting a value to 0, before your going to set it to 20, does not make sense. Or if memory block is going to be overwritten by a picture, this why the C language does not automatically initialize the variables or the memory, it’s faster to not clear the memory first, the fact that memory is not cleared before use, has been known to be exploited in more protected operating systems. To get access data from memory of another user on the same system. There are other exploits in caches as well.

let’s say code like:

if (win) CloseWindow(win);
if win has a unknown value, then CloseWindow will peak around in memory that was not allocated, and program will crash.

Another case where often crashes, if for example your coping text and forget to terminate the destination string. It might work most of the time, but once in while there is not a 0 at end of destination string buffer and it crashes. It was not long a go a bug in Reaction text input classes was discovered to have bug like that.

So make sure to keep your OS up to date.

@amiganuts

When you have a DSI error, it can affect other programs, best to reboot. Pretty sure tool has reboot button, that should be hint.

Unless you know there is no bugs 100%.. and your where running the same program night and days, for a years without issues, not experience issues before, I wont point to other factors.

@amiganuts

Quote:

Probably not, it can indicate your missing system updates, or program not installed correctly.

Quote:

if you have stack corruption or not.
if Redzone is damaged or stackpointer is outside bounds,
this means you should increase stack.

Quote:

illegal machine code instruction, this typical happens when library was not opened, or when your using the wrong library version.

Quote:

When reading outside of allocated memory or writing to memory that was not allocated you get DSI error. This clearly indicates a bad pointer, if pointer got corrupted, or if memory was not allocated, or if bad calculation of size, lack boundary checking.

AmigaOS4.1 does know who’s memory it is unless its private memory, most memory is allocated as shared memory, and can be swapped out.

As you can understand this is extremely limited information, if your going to report a problem to the developer you need to provide the full debug log, as it can contain a stack trace, cpu register values and disassembly of the crash.

There is lot bad programs, the Grim Repair is telling you about a crashed programs, as user you can no longer interact with the program much. I suggest using Snoopy to check if program failed to open a library or font, or something, you might get lucky, discovering it just a missing file that was not loaded.

@Yodaphone

Congratulation with your Sam460, and welcome to our little AmigaOS4/PowerPC rebellion.

@Chris

Form what I have tested.

It renders pretty quickly, its stable (it did not crash), tried a few random sites.
but there is lots of rendering issues yet, I mostly tried Norwegian news sites, like:

https://vg.no
https://dagbladet.no
https://www.nettavisen.no/
https://start.no
https://www.dagsavisen.no/

I don’t normally look at these pages, as its full of clickbait news, and paywalls.
this was just because I was curios about how compatible browser is, mostly.

@MamePPCA1

I think JIT is slower if its 68040, you should try 68020