Zap Disassemble
Rick Murray (539) 13850 posts |
Double wrong. ;-) You provide a way to get a memory dump. How is this different to just passing the address of the error block to *Memory and reading it out of that? As Colin said, I was rather surprised that Reporter doesn’t have a method of dealing with error blocks directly – like “here’s a pointer, do something smart with it”… |
Steve Drain (222) 1620 posts |
As long as your application has provided the buffer, of course. ;-) More fully, Basalt deals with these cases this way:
Terminate at the first control character.
Terminate at address The statement |
Martin Avison (27) 1494 posts |
I will add that on my ToDo list. |
Fred Graute (114) 645 posts |
As I seem to be chasing bugs in other editors lately (see here and here) here’s my fix for HidePtr. The original code has a problem with The problem is not in If the value in r12 is such that bit 28 is set then we’ll return to the OS with V set, with r0 possibly being seen as an invalid error pointer.
To fix the problem I’ve changed the bytev code to the following. Where we restore ‘our’ flags before calling other claimants and let them sort out ‘their’ flags.
With this change HidePtr seems to be okay but it’s hard to be sure. As Rick says: It starts off okay, then gets a bit weird, than goes all out crazy-gonzo. |