OSLib bug fixes (various)

[Tony van der Hoff]

On Mon, 15 Jan 2001, at 10:11:23, Daniel Ellis <Daniel.Ellis at pace.co.uk>
wrote on the subject "OSLib bug fixes (various)":

>On Fri 12 Jan, Tony van der Hoff wrote:
>> >
>> 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.
>
Interesting. I'm running RO4.02, SCL 4.87. The first word is indeed not
zero (&e59ff400); I guess the first byte being 0 is sufficient.

Anyway, as I said previously, Timothy is quite right; I shouldn't be
passing null pointers to sprintf, even if it happens to work on my
system, so it's all academic :-)

-- 
Tony van der Hoff         |  mailto:OSLib at mk-net.demon.co.uk
Buckinghamshire, England  |  http://www.mk-net.demon.co.uk/oslib/
----------------------------------------------------------------