Take a look at YAM's source. It uses lots of additional signals for different purposes. The Wait() call is located in line 2785 and the handling of the received signals follows directly after that. There is absolutely no need to "eliminate" certain signals using SetSignal().

@JosDuchIt

You are trying to tokenize a constant string, which is impossible since strtok() will modify the string. The crash you are getting is because strtok() is trying to write to read-only memory. The crash log, which you never made public here, should have exposed this.

The man pages included in Ubuntu Linux contain these warnings for strtok():

Quote:

No problem here using MUI-OWB for AmigaOS4. It looks the same as in Firefox and loads quite fast, even across my dead slow connection.

YAM is not developed by me alone, although I did most of the recent stuff. There are other developers who might have fixed such bugs in the meantime. And even if bugs don't get fixed immediately the bug tracker will not forget about them (in contrast to you or any other human).

So please, use YAM's bug tracker. Preferrably non-anonymous to let us ask further questions and to let you be notified about the progress.

@ChrisH

Quote:

This is absolute nonsense. I can very easily rename a binary executable to "picture.png", but this will not change the type of the file. It will not be a PNG image from that moment on, even if Windows will try to treat it as such. The contents define the type of a file, not its name. The name is just hint, nothing more, nothing less.

@alfkil

Quote:

@alfkil

Your code is missing the setsockopt() call to tell the TCP/IP stack in which events you are interested in. Without that it has to assume you are interested in nothing and hence will never Signal() your application. Refer to the GetSocketEvents docs for more details.

@Antique

Take a look at YAM's source: http://trac.yam.ch/browser/trunk/src/MailList.c

The SortMailList() function will do exactly what you want. You just have to provide a suitable comparison function.

@Deniil

MUI of course.

@ChrisH

The public version of MUI3.9 needs to lock the screen to perform its DnD operation. But to avoid deadlocks it may finally give up and abort the DnD operation in favour of other applications.

This has been changed completely in the meantime and screen locking is only done when there is absolutely no other way. But on hi/truecolor screens with compositing enabled screen locking is never necessary.

The only drawback from your point of view is the fact that this version is still in beta testing and has not yet been released to the public. So please be patient.

@Deniil

The scheduled release date for YAM 2.6p1 is September 24th. The bug you mentioned, among lots of others, is definitely fixed there. Currently that updated version has been sent out to the beta testers for all supported systems to catch possible remaining bugs.

@Slayer

To be honest, better get a fast Linux machine and use zerohero's cross compilers on this. Linux will do the same work a lot of times faster.

You might argue about native development, but a 68k cross compiler running on OS4 is the same non-native development like a 68k cross compiler running on Linux.

@kas1e

Quote:

Of course MemGuard can capture such bugs on freeing only. How could it do that during the allocation? Think about it. A MemGuard hit during one of the Alloc#?() functions would mean the memory system itself is buggy and cannot even perform an allocation correctly. Especially something like damaged walls can only be detected if the application releases the memory back to the system.

MemGuard just remembers the parameters of the allocation call (function name, size, flags) and prints them during the free operation to give the developer a hint which allocation might have been affected. This information can be useful if the hits occurs with very certain allocations only.

@Mrodfr

Quote:

"DSI" means "data storage interrupt". It just means that an access to an invalid address happened. This can be caused by a gone-wild application which writes to random addresses or by an application which writes just one byte beyond its allocated buffer limits and the buffer is right at the end of a memory page.

MemGuard can report such errors upon a Free#?() operation only, while the DSI may happen at any time as soon as the invalid access happens. But as the name "interrupt" implies it is an interrupt. Interrupts must be handled fast and you cannot perform fancy stuff like wall checks, symbol look up, etc. The GrimReaper performs this task outside the interrupt.

Application might even write beyond a buffer and you won't get a DSI at all, because the write access still happened within a valid memory page. Such accesses can only be detected by MemGuard. But MemGuard slows down system performance a lot, because the system does lots of memory allocations. Thus the system itself is doing only some very quick checks. Everything else must be examined when there is a demand for a check, but not all the time.

@salass00

cp -p

@amigadad

This is a known issue. MUI locks the current screen hard during DnD operations. This behaviour is exactly the same since ages. The lock is necessary because the dragged object's image is drawn directly onto the screen and the lock guarantees that no other application can draw anything (and thus destroy MUI's dragged image). Unfortunately MUI's lock is not as uninterruptible as stunzi originally wanted it to be and other applications might break it. This leads to the aborted DnD operation as this is the only possibility to prevent deadlocks.

I am currently working an a solution for OS4, but this requires hi/true color screens and compositing enabled. With this solution there is no need for such a hard lock anymore.

@JosDuchIt

Having a working string edit hook is not really as hard as you might think. And you don't have to conjure up any obscure magic to make it work.

For example Scout's task signal window uses an edit hook to restrict the input to hexadecimal values only. All the "magic" happens in hex_editfunc().

@JosDuchIt

Use "-lm" only. For PPC there is no difference between FPU and non-FPU math libs, because all supported PPCs have an FPU.

@JosDuchIt

If you enable update checking in YAM you get notified as soon as a new version of YAM or its depending custom classes is available, along with their release notes.

@alfkil

Stack overflow?

If the program works without that additional line/variable, how much stack is used at most while running?