Announcing ZPdebug to make resolving ZeroPain errors in BASIC easier

Sometimes the only information from an error in BASIC are the contents of the machine registers. This is usually from a ZeroPain or Data Abort error, with the R15 PC location within the BASIC module.

Without the BASIC line number this makes diagnosis rather difficult and very time consuming.

ZPdebug aims to make this process a little easier. It can extract useful information from ZeroPain log files, and with a few clicks display the likely problem code from a source file or a running task.

This is a first public release of this utility, but it is a development of a process that has been used to identify many ZeroPain errors in BASIC programs.

It can be downloaded from http://www.avisoft.f9.co.uk
or https://homepages.force9.net/avisoft/
but note that https seems to give certificate errors using Netsurf or Iris, but is ok with Firefox!

It is also available on !Store.

but note that https seems to give certificate errors using Netsurf or Iris, but is ok with Firefox!

I think the server isn’t sending the intermediate certificate and the client is required to do a separate download or already have a copy.
Checks in Firefox show the “DigiCert Global Root G2” certificate already in the certificate store

@Steve: So do the certificate problems look like a server problem or a client problem?

Assuming what I’ve noted is the case, technically, the server is entitled to provide the pointer to the location to download rather than including it with.

If you ensure the RO client has a copy of the intermediate certificate in its own certificate store and the problems on your client go away then the difference in behaviour for Firefox is a setting in Settings, Privacy & Security, Certificates which is: “Allow Firefox to automatically trust third-party root certificates you install” which I don’t think the RO clients have.
Explanation of what that does here

The certificate chain is incomplete in any case…

https://www.ssllabs.com/ssltest/analyze.html?d=homepages.force9.net&s=212.159.8.90&hideResults=on
and:
https://www.ssllabs.com/ssltest/analyze.html?d=homepages.force9.net&s=212.159.9.90&hideResults=on&latest

So do the certificate problems look like a server problem or a client problem?

Technically it’s the server not having the certificate chain properly configured. Chrome uses AIA fetching to get the intermediate. https://www.thesslstore.com/blog/aia-fetching. Firefox uses something similar.

SSL checker shows the problem. https://decoder.link/sslchecker/homepages.force9.net/443

@Chris: Thanks for that. Some evidence to throw at Plusnet!