Re: [StrongED] Testing StrongHelp 2.90b1 (Urgent)

[Peter Young <pnyoung@xxxxxxxxxxxx>]

On 19 Mar 2017  Fred Graute <fjgraute@xxxxxxxxx> wrote:

> In message <mpro.on2uay0eacn5o01zg.lists@xxxxxxxxxxxxxxxxxx>
>           Steve Fryatt <lists@xxxxxxxxxxxxxxxxxx> wrote:

>> On 19 Mar, Peter Young wrote in message
>>     <57475b1f56.pnyoung@xxxxxxxxxxxxxxxxxxxx>:
>> 
>>> ARMX6, RISC OS 5.23, RComp version.
>>> 
>>> All initially going swimmingly here. OK with Help on StrongHelp itself,
>>> then NeXTBar and Transient. Then with PrintPDF:
>>> 
>>> 18-Mar-16.19 Mar 17:03:07 000 80000002: Error from StrongHelp: Internal
>>> error: abort on data transfer at &2058CE28
>>> 
>>> *where Address &20517E28 is at offset &0000D314 in module 'StrongHelp'
>>> 
>>> *showregs Register dump (stored at &2000BD70) is: R0  = FFCDD0B1 R1  =
>>> 00000480 R2  = 0000A154 R3  = 58011190 R4  = 00000000 R5  = 00000013 R6  =
>>> 00021DF0 R7  = 000203B0 R8  = 00000480 R9  = 99119999 R10 = 0000AD3C R11 =
>>> 00000480 R12 = 2021DA2C R13 = 2021F1A8 R14 = 2050F3A4 R15 = 20517E28 Mode
>>> USR32 flags set: NzcvqjggggeAift        PSR = 80000110
>>> 
>>> I hope this means something useful!

> Thanks for reporting this. It is a bit confusing though as the abort
> address given is different from the one shown by *showregs. Assuming the
> latter address is correct then the bug is somewhere in the flex manager.

>> Which version of PrintPDF are you using, as the manuals differ between
>> versions? Which page are you viewing when this happens, and where does one
>> need to click to get the problem?

> Those would be my questions too. If the problem is indeed in the flex
> manager then it's even more important to know the exact steps to
> reproduce this as it may depend on the state of the entire flex heap.

>> I've just tried it quickly, and can't reproduce the issue -- meaning that
>> either we're doing something different, it doesn't affect a Beagleboard, or
>> there's something else involved in triggering the crash.

> Tried PrintPDF 1.11 here, no abort either.

I've just reported trying the same steps with PrintPDF 1.11, and I 
can't reproduce the crash. Apologies both to Fred and to Steve, but 
why this should have happened I have no idea. I will go on using 
StrongHelp 2.091b and will report any other weirdnesses, if they 
happen, which I imagine they won't.

Best wishes,

Peter.

-- 
Peter Young (zfc Ir) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@xxxxxxxxxxxx

--=20
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxx
List archives at http://www.Torrens.org/RO/StrongED/index.html