Debug Log for Programs?

I am trying to find some sort of debug log for RiscOS. I am trying to run Fireworkz and it keeps crashing whenever I try to change the font or font size. I know on other platforms there are system monitors that will show you what module failed or if it’s just missing a library.

Anything like that exist for RiscOS? The error I am getting is an “Address Exception”.

You’re running on a Raspberry Pi? Are you sure Fireworkz is 32 bit compliant?

Generally if it’s a missing module, that will be reported nicely, but as far as I know, there is no such thing as a system wide log.

Ok, yes it’s 32bit compatible. I even have Aemulor Pro in case it wasn’t. I tried running the app under Aemulor and when it crashed, it crashed hard, no recovery had to power cycle. I even tried different CPU modes from the !Configure app and no luck their either.

The latest version of Fireworkz is definitely ARMv7 compatible, and runs fine on the BeagleBoard, so there is no reason it wouldn’t run on PandaBoard or Raspberry Pi (haven’t tried the latter two, but I am sure others are using it on that hardware – I could try later today).

Are you sure Fireworkz is 32 bit compliant?

Chris says yes – but is it the Iyonix version or the very latest ARMv7 compatible version?

Generally if it’s a missing module, that will be reported nicely, but as far as I know, there is no such thing as a system wide log.

Hmmm, maybe someone could usefully do something bringing the full capabilities of Syslog to RO5
(The other branch has had a wider Syslog implementation for quite a while)

I have a pile of utilities that list various Important Things – vector claimants, callafters, voices etc. I always present the code addresses in a module-relative fashion where possible. ie FontManager+&4C10.

Considering the ubiquity of *WHERE immediately after an exception it’s a pity that’s not standard practice – Address exception at FontManager+&4C10 for example.

Mind you, I also have CLIs on the major exceptions (such as Branch through zero) so maybe this is a job for a module. Hmmm…

I believe that latest version of Fireworkz has a facility for enabling some debugging to my Reporter – which is one facility for reporting errors and debugging information. See FW docs for info how to enable. See www.avisoft.f9.co.uk for details of Reporter.

So I figured out the issue. When I updated my system to RC12, I had a fresh install of RISCOS, so I just downloaded a fresh copy of Fireworkz, to my surprise it ran just fine. When I had transferred all of my apps and data back over, I tried it again. It crashed. I then thought back to what apps I have running at startup, the issue is with !Organizer. If it’s open and I run Fireworkz, then Fireworkz crashes. If !Organizer is closed, then there are no issues. Upon googling it seems to be an issue with v2.07 and below of !Organizer. Case closed but will check out the software.

Thanks!