Small bug

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Small bug

Ian Bartholomew-21
I'm seeing a strange error after a change log compress.

Start a clean image.
Do a Compress Changes.
Exit _without_ saving the image.
Restart the image.

I get the following walkback every time

22:09:18, 24 November 2005: 'Must be boolean'
SmallInteger(Object)>>error:
SmallInteger(Object)>>mustBeBoolean
InputState>>aboutToIdle
InputState>>waitForInput:
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>on:do:
[] in BlockClosure>>newProcess

A bit of debugging shows that in InputState>>aboutToIdle the initial
call to uiIdle answers 1, rather than a Boolean.  However, looking at
the code for uiIdle I can't see how it can possibly answer 1 - so I'm
going to bed!.

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.


Reply | Threaded
Open this post in threaded view
|

Re: Small bug

Bill Dargel
Ian Bartholomew wrote:
> A bit of debugging shows that in InputState>>aboutToIdle the initial
> call to uiIdle answers 1, rather than a Boolean.  However, looking at
> the code for uiIdle I can't see how it can possibly answer 1 - so I'm
> going to bed!.

I have a vague recollection of running into this once a few months back
in D5. I looked at the code for a bit and remember thinking "this is
impossible". As I didn't have any way to repeat what had happened, I
just let it go. Glad to hear you found something that can reproduce what
appears to be the same problem!

--
Bill Dargel            [hidden email]
Shoshana Technologies
100 West Joy Road, Ann Arbor, MI 48105  USA


Reply | Threaded
Open this post in threaded view
|

Re: Small bug

Ian Bartholomew-21
In reply to this post by Ian Bartholomew-21
I've just noticed that I get a different walkback if I do the following ...

Load a clean image
File in my image setup script
Compress the change log
Clear and close the Transcript
Save the image under a different name
Exit

If I open up the original image again I get

08:18:32, 25 November 2005: 'DeadObject does not understand
#valueWithArgumentsAt:'
DeadObject(Object)>>doesNotUnderstand:
ExternalCallback class>>callback:withArgumentsAt:
[] in ProcessorScheduler>>callback:withArgumentsAt:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:withArgumentsAt:cookie:
InputState>>topLevelHandlesDo:
InputState>>uiIdle
InputState>>aboutToIdle
InputState>>waitForInput:
InputState>>loopWhile:
InputState>>mainLoop
[] in InputState>>forkMain
ExceptionHandler(ExceptionHandlerAbstract)>>markAndTry
[] in ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>ifCurtailed:
BlockClosure>>ensure:
ExceptionHandler(ExceptionHandlerAbstract)>>try:
BlockClosure>>on:do:
[] in BlockClosure>>newProcess

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.