OSLib bug fixes (various)

[Daniel Ellis]

On Fri 12 Jan, Tony van der Hoff wrote:
> On Fri, 12 Jan 2001, at 16:52:26, Stewart Brodie
> <stewart.brodie at pace.co.uk> wrote on the subject "OSLib bug fixes
> (various)":
> 
> > > What I mean is  printf( "%s", NULL ) behaves the same way as printf(
> > > "%s", "" )
> >
> > Not under RISC OS it doesn't - you get oflaoflaofla in the former case. 
> > Byte 0 of RAM is not a zero byte and the C library does not trap accesses
> > to it.
> >
> OK, so how do you explain this working as I describe:

I get:

*RAM::RamDisc0.$.data1.Printf.!RunImage  Null string
ÌòŸåÌòŸåÌòŸåÌòŸåÌòŸåÌòŸåÌòŸå2¦ ã8 Êå|Dð^â
ÌòŸåÌòŸåÌòŸåÌòŸåÌòŸåÌòŸåÌòŸå2¦ ã8 Êå|Dð^â*

Just running your binary.  Even on freshly booted RISC OS 3.7 machine.  If
you don't see this then I guess you must have a different version of the
shared clibrary or something.  It's hard to imagine that you've got 0 as the
first word of memory, but I suppose it's just about possible.

-- 
Daniel Ellis, Senior Software Engineer,
Pace Micro Technology plc,
645 Newmarket Road,                               tel: +44 (0) 1223 518619
Cambridge, CB5 8PB                                WWW: http://www.pace.co.uk/