Debugger bug?

Blair,

The debugger's implement-in menu is blowing up (walkback below).  I have
seen this a few times before, but perhaps never realized that it was
generating the menu that lead to the problem - my first thought after
something like this is about how to get out w/o saving the image but w/o
losing work =:0

Appologies if this is old news.

Do you have an update on PL4 and the block tempories fix?

Have a good one,

Bill


7:53:36 PM, Thursday, February 19, 2004: Unhandled exception - a
MessageNotUnderstood('BlockFrame does not understand #base')

BlockFrame(Object)>>doesNotUnderstand:
BlockFrame>>argsOffset
BlockFrame(StackFrame)>>argAt:
[] in BlockFrame(StackFrame)>>arguments
Interval>>collect:
BlockFrame(StackFrame)>>arguments
Debugger>>populateImplementMenu:
Debugger>>onAboutToDisplayMenu:
Menu>>queryAllAlong:
Menu>>queryAllFromView:
ListBox(View)>>wmInitMenuPopup:wParam:lParam:
ListBox(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
Menu>>showIn:position:
ListBox(View)>>trackContextMenu:
ListBox(View)>>wmContextMenu:wParam:lParam:
ListBox(View)>>dispatchMessage:wParam:lParam:


--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Bill Schwab" <[hidden email]> wrote in message
news:40355d0d$[hidden email]...
> Blair,
>
> The debugger's implement-in menu is blowing up (walkback below).  I have
> seen this a few times before, but perhaps never realized that it was
> generating the menu that lead to the problem

This (well the underlying cause) was patched in 5.1.2 according to our bug
tracking system (#1296). The only senders of #base in a 5.1.3 image are in
SAFEARRAY.

>...- my first thought after
> something like this is about how to get out w/o saving the image but w/o
> losing work =:0
>

Well you could try turning on the image backup option and then having saved
and exited, copy the backup somewhere safe before restarting so that you
know you can return to it should there be a problem in the latest save.
Personally I prefer to run without the backup because it makes the image
save too slow. I rely on the change log and Ian's Chunk Browser to recover
work when I don't save the image.

> Appologies if this is old news.
>
> Do you have an update on PL4 and the block tempories fix?

No, but I'll probably make the modified compiler available for download when
it is done.

Regards

Blair