Bug in AmigaOS 3.9 ram-handler ?

[ncafferkey]

I don't think Thomas Richter wrote the ram-handler.

I wrote a test program just now, and got a crash too. However, I found that if the second attempt to lock the record (exclusively) is done with REC_EXCLUSIVE_IMMED, it doesn't crash. Maybe this could be a useful work-around for you.

[ncafferkey]

I think lempkee was responding to prowler's post, which had nothing to do with the main topic of this thread.

I've tested to use the REC_SHARED_IMMED and the REC_EXCLUSIVE_IMMED flags and they work. Ok that's fine so far, but life would be some much easier, if I could wait for a timeout and let the Ram-Handler awake my process, if the timeout is elapsed or the lock is free...
It's hard to do this on my own, this would lead to something like "polling": looking every 1/10 of a second if the lock is free now...that is not very multitasking-friendly

Even if the timeout modes worked, I think the maximum timeout you can specify is 50 ticks, so you'd still have to poll every second.

I can't actually see why you need to lock records twice with different handles. Are you sure there isn't a better way to achieve what you're trying to do?

[ncafferkey]

Does the problem with the RAM-handler only arise when more than one program is using your library? If so, is this not acceptable given that that the bug isn't in your code. People will still be able to use it with the RAM-handler most of the time.