@Mrodfr

Oops I forgot a word : Quote:...

@Mrodfr

Can I add that if you are doing the kind of things described in this other thread (that I told you wasn't recommended) your problem might be caused by your system configuration.
Can you try the same tests cold booting from the AOS 4.1 (I insist on the cold booting because if you replaced some of your kickstart modules by others older versions a simple software reboot won't be enough).

@Mrodfr

No one referred to AOS 4.0 except you. I think you didn't understand well what alfkil said : DEbug 101 will not work under AOS 4.1 update 1 nor under AOS 4.1 update 2 due to a bug in elf.library on this systems. On the other hand elf.library.kmod from a *plain* AOS 4.1 (no update installed) doesn't contain this bug (as the latest - yet unreleased - version v53.13) and will enable to run the program.

So if you really want to run this debugger then either replace your elf.library.kmod by the one from the AOS 4.1 CD (not very advised, as you'll loose the features introduced since then at the same time which might very well prevent some other programs to run reliably or run at all) either wait for an update with the latest elf.library (advised).

@ssolie

Thank you for such a detailed technical information, that's very valuable !
That's somehing that would worth to be included in the Migrating guide PDF included in the SDK (or even better in a small new "BOOPSI 4.x quick guide" document)

I never paid great attention until recently but currently the timestamp applied to post is not accurate, I don't know what is displayed.
Currently my local time is 16:58, I'm on Paris timezone with DST enabled (which means GMT+1 +1h DST => GMT+2).
My account is configured correctly with the timezone.

EDIT: and the post timestamp is 13:58:33 which has nothing to do (approx GMT-1).

@Mrodfr

A debugger won't do what you are saying. A debugger only helps a developper to find bugs by allowing him to run the program step by step, see which execution path it takes and examine change in any variable. It's purpose is not to produce readable output when a program crashes.

For that Grim Reaper is here. Yes sometimes the system is completely halted so log can't be stored and that's a problem (which can generally be worked around by hooking up another computer via serial link and capturing the output). If a programmer is lost with a Grim Reaper log then either:
- it's because he does not really develop/use AOS4, only cross-compile his program for it, and so isn't familiar with its output;
- it's because he didn't do the right thing to produce a debug information enabled version of his program, so unless he's very good at dessassembly and register dump reading yes he won't be able to spot the location of the bug, (with a correctly produced debug version a Grim Reaper log will allow the programmer to retrieve the filename, the function name and the line code the crash occured);
- both of the previous.

@Mrodfr

Okay so in fact you are asking alfkil to add the possibility to pass a commandline to the debugged program prior to its execution.

This is indeed a good feature request.

@Mrodfr

Okay so basically you are asking if the whole program or only some of its functions are incompatible with current public AOS 4.1 versions, aren't you ?

@Mrodfr

I think alfkil means that due to problems in elf.library present in AOS 4.1u1 and AOS 4.1u2 his program only works on plain non updated AOS 4.1 or on latest AOS 4.x beta.

For the rest I don't understand your example about unrar.

@Mrodfr

Maybe because internals changed so much that it would cost more to try to update snoopdos so that it still works under AOS4 than to develop a new program from scratch.

Especially if one wants to share source code with other Amiga like systems it would either be an horror to maintain (full of #ifdef) or only the least common API each platform still share with each others (so least powerfull)...

@Mrodfr

Snoopdos replacent is Snoopy, not every functions from SnoopDOS are present yet but maybe asking kindly Colin the one you miss and he might add them...

@mr2

Why not use OS4Depot crashlog facility it will help trace problems.

@alfkil

It's very much welcomed !!! Great !

I discovered a little problem though select the provided HelloWorld sample, run it, then when the display says execution ended, if I click on "Set breakpoint" Debug 101 is reaping and can't be used any further.

I briefly tried to debug "DEbug 101" while debuging "Hello World" but wasn't able to spot where the problem occurs (it was late and was needing a good sleep).

Anyway I wish you good luck it's promising !

@billt

are you wanting only a binary or the whole sources ?
Anyway MickJT have both and binary archive is online and directly downloadable, while for the source archive you must PM him.
All you need is in this thread : http://www.amigans.net/modules/newbb/ ... t_id=56044#forumpost56044

@tonyw

I'll even add that http://crashlog.os4depot.net/ is there for that purpose so even a cut down version should not be posted here but on that site instead and then here one just have to post a link.

@kas1e & cha05e90

It's long time source code is available for MetaView, don't rememeber if it was on his website or on Aminet, anyway I have it somewhere on my HD, if you can't have an answer from the author, nor you can find it I can try to dig it out.
(I downloaded this to port it to AOS 4 too but never found the time to even look at the source code )

@JosDuchIt

Search for the 'Update' preference programm in your sys partition and then uncheck the 'Docky mode' that should allow you to see the gui at startup.
Anyway once AU is in AmiDock you can easily open it using right mouse button and selecting the appropriate menu item (not in front of it right now so could not tell you exact label).
Normally if AmiUpdate does find some updates for your computer its icon in AmiDock will show a small warning in the bottom right corner, it should also issue a Ringhio notification that can be clicked on to open the gui...

@Rogue

Quote:

Yes all this pthreads thing started because I was giving threads as an example of suffs I'd like to see in AOS APIs and mrodfr answered that pthreads.library already exists.[/quote]

@Mrodfr

I'm not questioning the fact pthreads is working, but rather wondering on a *developer level* how it will interact with the rest of AOS APIs.

@tfrieden

Quote:

Nothing special... except it does not feel really integrated into the AOS API and I do not feel confident using it for writing handlers. But I didn't dig into it more than that, may be I'm mistaking ?

EDIT: not to say that currently this is not really threads but processes that we would get with our pthreads implementation.