Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Martin Wuerthner Newsgroups: comp.sys.acorn.programmer Subject: Re: Problem with longjmp on A9 Date: Mon, 11 Jul 2011 11:39:18 +0200 Organization: MW Software Lines: 42 Message-ID: References: X-Trace: individual.net yrZIGLf2TGZJh8eOhi2bIAidM5DXtKoUrhtDY+dSPVcorswCtB X-Orig-Path: bach.planiverse.com%martin Cancel-Lock: sha1:LMJ20UbRCOtZEbUanS6f22np6Dg= X-Editor: EmailEdit 6.00 User-Agent: Messenger-Pro/6.00 (MsgServe/6.00) (RISC-OS/5.16) NewsHound/v1.50-32 Xref: x330-a1.tempe.blueboxinc.net comp.sys.acorn.programmer:543 In message Matthew Phillips wrote: > I have been trying to track down a difficult bug in my software which only > affects users of the A9Home computer, specifically an A9 running "RISC OS > Select 4.42 kernel 8.68". The Shared C Library version is "5.59 (04 Mar > 2006) 32bit only". The same user has a RISC PC with Select 6.10 kernel 10.49 > and Shared C Library "5.63 (11 Mar 2007) 26bit only" on which the problem > does not occur. It does not occur on the Iyonix or Beagleboard either. > After investigating, I can only conclude that the A9's Shared C Library is > not fully restoring the context saved at setjmp when a subsequent longjmp is > executed. Let me set out my reasoning and if anyone finds any holes in it, > please let me know. That is a known problem that I have reported to Ad6/ROL in 2006. longjmp is indeed broken on the current A9home ROM image (Select 4.42, CLib 5.59), but also on the previous A9home ROM image (which had CLib 5.02). That problem affects the exception handling in Easi/TechWriter and can lead to arbitrary failures of these applications on the A9home. That is the reason why I still advise users in the documentation that EW/TW has beta status on the A9home. > Has anyone else had this sort of behaviour? Are there any alternative > explanations before I take this up with ROL? > I'm not very familiar with the A9: would it be possible (or indeed advisable) > to softload a different version of the Shared C Library? Yes, that should be possible. It was not an option in 2006 because there was no such version available for public distribution (the softload CLib for the Iyonix could not be used), but it should be easy enough nowadays to build a suitable CLib from the ROOL sources. -- Martin --------------------------------------------------------------------- Martin Wuerthner MW Software http://www.mw-software.com/ RISC OS Software for Design, Printing and Publishing ---------------------------------------------------------------------