"Someone is working on XYZ for ARM"

or

"We have KLM"

So I still doesn't know if a bounty for a crash ahndler would make sense.
I still have no one who could help me to write a bounty text.

CU
GreenNight

We have had Suspend/Reboot in x86 for some time also now.

Quote:

not using aros much atm, so i don't know if it's already in the nighties, but what about that:

if you look at this thread
http://aros-exec.org/modules/newbb/viewtopic.php?post_id=50298#forumpost50298
you can at least see some suspend/reboot requester in arm build!

here's a thread regarding this:
http://aros-exec.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=4067&forum=2

other - thought sonic was already working on some of it...

If you read the commit log messages, sonic has been busy making all the kernels modular (only ppc and x86_64 used to be), and now has to do some memory protection related changes to dos.library for his arm-IOS hosted port.

I missed this, but see PM

Why is this thread ignored ?

[_] Don't like the idea of a crash handler
[_] Don't like to discuss a bounty
[_] Don't like the poster of the idea
[_] Other reason (please explain)

I still want to have some kind of crash handler.

I once started a bounty that no one interested (MP3 Player) so I had the idea to discuss possibilities first before starting another useless bounty again.

The crash handler should:

1.
Be activated on exceptions, or on illegal behavior of a task.

- division by zero
- illegal call values for system function like AllocMem(),
- illegal read write access to unused memory addresses via MMU ( as good as possible )
- ...

2.
It should report why it was called on a Window, Alertbox, Screen or whatever, the report should contain:

- reason for calling
- the name of the program /process that caused the trouble
- informations about memory used by this process
- informations about open files
- ...

3.
The window of the crash handler should allow to:

- End the process that caused the troubles.
- end the window of the crash handler
- ...

4.
The crash handler should have an interface to be used by user programs for reporting severe errors or troubles.

5.
The OS will need some extensions for a basic MMU handling, and some basic resource tracking.
The crash-handler should be available for AROS x86.

6.
The crash handler should be configurable by the user via some parameters in the user-startup. It should still be possible to switch it of.

--------------

For setting up the bounty, I need some help from people understanding more about AROS than I do. The crash handler should improve AROS's stability but starting a bounty with to high requirements could be as useless as starting a bounty that would no bring any benefits to the system.

CU
GreenNight