Sargasso 2.10 and ZeroPain

I recently put the latest version of Sargasso 2.10 (same appears to apply to v2.09 as well) on my 4te2 (Pi4B) and discovered it appears it is genrerating ZeroPian log.

Can others confirm this? Can anyone fix it?

https://www.riscosopen.org/wiki/documentation/show/Reporting%20bugs

Include also the pain log entry (but if there’s a load of endlessly repeated junk, you can omit that).

Thanks Rick, but is that not for reporting bugs in the OS itself? It’s a third party application generating the ZeroPain.

Also do others get the ZeroPain for Sargasso on Pi4B.

Pretty much any bug report starts with the same basic actions – describing what, when, how, where.

So:

• What are you doing? Loading Sargasso? Using it? What?
• What does the pain log say?

It’ll be harder to get the memory as Sargasso is a Wimp app so memory you see in app space won’t be the same (but see the next message).

So let’s see what the log says first.

I can’t report as I don’t have a Pi4, and I’m writing this on Android while making linguine (comfort food FTW!), but since you have a zero pain log, that’s where to start looking.

If you want to be more adventurous, kill off ZeroPain so Sargasso actually crashes out, and then set up a Debugger Annotated Exception dump, then get it to crash and let Debugger record what happened.
https://www.riscosopen.org/wiki/documentation/show/Debugger%20Exception%20Dumps

Thanks Rick, but is that not for reporting bugs in the OS itself?

Not really, as the “Bugs in 3rd party software” heading half-way down makes clear. However, if you must have a non-ROOL explanation of why your “bug report” wasn’t that helpful to anyone, try https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Rick, to answer your question, I was simply running the program. It does not crash or display any error, just puts text into the Zeropian text file. I noticed this with v2.09, and discovered that there was now a v 2.10, so installed that and that also runs and puts text into the ZeroPain file. Note: It still works fine even if the ZeroPain module is not active.

I was asking if anyone else has noticed this before sending the file to the person who i think is now maintaining it.

Steve, it was NOT intended to be a bug report as I keep asking has anyone else seen the issue. So I know it not just me having an issue with my setup. I know how to log a bug report and have done so on a number of occasions to developers.

Chris, I’m using Sargasso 2.10 on a Pi4B, RISC OS 5.29 (13-Dec-22) – no issues – AFAIK.

Thanks Andrew. Yes the ZeroPain seems to be related to Sargasso’s Log file, but does not stop the application working. Sargasso keeps the logfile open all the time it is running.

I will send the ZeroPain log to Chris Gransden who I believe now supports it, unless anyone knows different. So he can investigate further.

Note: It still works fine even if the ZeroPain module is not active.

Ah, so ZeroPain restores the compatibility page on exit so things “just work”.

as I keep asking has anyone else seen the issue. So I know it not just me having an issue with my setup.

And I kept asking what the log saud, because sadly RISC OS does have a habit of slaughtering foreground applications when background stuff crashes, which the log might have possibly indicated.

The below is from the ZeroPain Text file. This seems to be repeated

Time: Tue May 16 11:37:45 2023
Location: Application space
Current Wimp task: Sargasso
Last app to start: <Sargasso$Dir>.!RunImage ><Sargasso$Dir>.Sargasso/Log 2>&1

R0 = 00000000 R1 = 00818715 R2 = 00000000 R3 = 00000001
R4 = 007e2e70 R5 = 006931c4 R6 = 00000000 R7 = 008186b8
R8 = 008186b8 R9 = 005df014 R10 = 005ee208 R11 = 005eed0c
R12 = 00683ff8 R13 = 005eec38 R14 = 00008554 R15 = 004c9cd0
DFAR = 00000000 Mode USR32 Flags nZCv if PSR = 60000110

004c9c88 : 01a0f00e : MOVEQ PC,R14
004c9c8c : eaffffc6 : B &004C9BAC
004c9c90 : e1a00000 : MOV R0,R0
004c9c94 : e1a00000 : MOV R0,R0
004c9c98 : e1a00000 : MOV R0,R0
004c9c9c : e1a00000 : MOV R0,R0
004c9ca0 : 6c727473 : LDCVSL CP4,C7,[R2],#-460
004c9ca4 : 00006e65 : ANDEQ R6,R0,R5,ROR #28
004c9ca8 : ff000008 : Undefined instruction
004c9cac : e1a00000 : MOV R0,R0
004c9cb0 : e1a00000 : MOV R0,R0
004c9cb4 : e1a00000 : MOV R0,R0
004c9cb8 : e1a00000 : MOV R0,R0
004c9cbc : e1a00000 : MOV R0,R0
004c9cc0 : e2102003 : ANDS R2,R0,#3
004c9cc4 : e3a03001 : MOV R3,#1
004c9cc8 * e710c002 * LDR R12,[R0,-R2]
004c9ccc : e1833403 : ORR R3,R3,R3,LSL #8
004c9cd0 : e1a01000 : MOV R1,R0
004c9cd4 : e1833803 : ORR R3,R3,R3,LSL #16
004c9cd8 : 1a00001c : BNE &004C9D50
004c9cdc : e05c2003 : SUBS R2,R12,R3
004c9ce0 : 2022200c : EORCS R2,R2,R12
004c9ce4 : 21d32002 : BICCSS R2,R3,R2
004c9ce8 : 05b12004 : LDREQ R2,[R1,#4]!
004c9cec : 1a00000f : BNE &004C9D30
004c9cf0 : e052c003 : SUBS R12,R2,R3
004c9cf4 : 202cc002 : EORCS R12,R12,R2
004c9cf8 : 21d3c00c : BICCSS R12,R3,R12
004c9cfc : 05b1c004 : LDREQ R12,[R1,#4]!
004c9d00 : 1a000009 : BNE &004C9D2C
004c9d04 : e05c2003 : SUBS R2,R12,R3

You’re welcome. On re-reading the whole thread- I don’t see a ZeroPain log file.

Where are you seeing the log file?

What version of RISC OS are you using?

Sometimes a log file will provide clues- errors, warnings. What does it say?

On re-reading the whole thread- I don?t see a ZeroPain log file.

I downloaded the ZeroPain module from the ROOL site its in the bonus binaries.

Where are you seeing the log file?

It will appear on the root of your drive if it generates a ZeroPain issue.

What version of RISC OS are you using?

I am using a 4te2 (a Pi4B) and RO 5.29 (June 2022), tried a newer ROM and same issue.

Not sure if it’s the same issue reported here. A zero pain can happen when using an Exclude filter on author and the feed doesn’t have an author.
Now fixed. Thanks.
A new version should appear in PackMan soon.

Ah thats interesting, as i do have a Exclude filter for the infamous DavidS who spammed these forums endlessly. I will remove it now and see what happens.