Re: Chevrons [getting OT] - and back on topic again
Re: Chevrons [getting OT] - and back on topic again
- Subject: Re: Chevrons [getting OT] - and back on topic again
- From: Richard 23 <email@hidden>
- Date: Fri, 5 Jan 2001 08:15:55 -0800
>
So, is this a known bug, am I the only one to encounter it, is there any
>
solution?
I've never gotten a crash from it but it does cause flashbacks in the
event log. The weirdest result I got back was odd enough to send to
Apple.
I got several screenfuls of this sort of thing:
"*A\,d6
moveq #$00,d5
tst.l d4
beq.s [xxK
`\,d6
beq.s n! |}x|f+x|~3x#NxK$eM`\,d6
tst.l d4
beq.s D\,d6
moveq #$00,d5
tst.l d4
beq.s j"
wow, even ResEdit doesn't disassemble CODE resources!
when compared to ascii character 0 the result was still true.
I'll bet this has everything to do with c strings being terminated with
ascii 0, and pascal strings which start with a single byte specifying
its length. ascii 0 is being misinterpreted so the next memory location
(probably free space containing jumbled garbage data). When unknown
data is interpreted as something that's supposed to make sense one never
knows where a legitimate end is going to be found. I switched to using
255 as the starting point for a unique delimiter. 0 is just to freaky.
R23