The attached changeset fixes two debugger problems introduced by 5308ContextEnh-ajh: 1. highlighting of decompiled source (do-its). 2. stepping over exception signals.
Cheers, Anthony
Anthony Hannan ajh18@cornell.edu wrote:
Ned Konz ned@bike-nomad.com wrote:
On Sunday 06 July 2003 10:47 am, Lic. Edgar J. De Cleene wrote:
Actualizing image from 5259 I notice debugger is not working as usual. Following code in step mode not highlighting . Not sure is a bug or I'm doing some mistake.
It's not following code in DoIts any more.
I'll fix this and the step over signal problem, soon.
Cheers, Anthony
In my image, I'm now getting walkbacks when a process is terminated.
Specifically, I have OSProcess installed, and it's got a process that it terminates in its startUp method.
However, that process's suspendedContext is nil.
Here's the call stack:
VM: unix - Squeak3.4 of 1 March 2003 [latest update: #5170] Image: Squeak3.6beta [latest update: #5331]
UndefinedObject(Object)>>doesNotUnderstand: #activateReturn:value: Receiver: nil Arguments and temporary variables: aMessage: activateReturn: [] in BlockContext>>newProcess value: [] in UnixOSPro...etc... Receiver's instance variables: nil
Process>>activateReturn:value: Receiver: a Process in nil Arguments and temporary variables: aContext: [] in BlockContext>>newProcess value: [] in UnixOSProcessAccessor>>grimReaperProcess Receiver's instance variables: nextLink: nil suspendedContext: nil priority: 40 myList: nil errorHandler: nil
Process>>return:value: Receiver: a Process in nil Arguments and temporary variables: aContext: [] in BlockContext>>newProcess value: [] in UnixOSProcessAccessor>>grimReaperProcess Receiver's instance variables: nextLink: nil suspendedContext: nil priority: 40 myList: nil errorHandler: nil
Process>>popTo: Receiver: a Process in nil Arguments and temporary variables: aContext: nil callee: [] in BlockContext>>newProcess Receiver's instance variables: nextLink: nil suspendedContext: nil priority: 40 myList: nil errorHandler: nil
--- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #activateReturn:value: Process>>activateReturn:value: Process>>return:value: Process>>popTo: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Process>>terminate UnixOSProcessAccessor>>finalize UnixOSProcessAccessor>>initialize OSProcessAccessor class>>startUp
< I'm a bug-fixing machine! >
This post brought to you by the BugFixArchiveViewer, a handy tool that makes it easy to comment on proposed fixes and enhancements for Squeak. For more information, check out the Web page for the BugFixArchiveViewer project: http://minnow.cc.gatech.edu/squeak/3214
< I'm a bug-fixing machine! >
On Mon, Jul 07, 2003 at 11:50:01AM -0800, ned@bike-nomad.com wrote:
In my image, I'm now getting walkbacks when a process is terminated.
Specifically, I have OSProcess installed, and it's got a process that it terminates in its startUp method.
However, that process's suspendedContext is nil.
Here's the call stack:
<snip>
I loaded the ContextCleanupDebugFix change set into an image with OSProcess installed, and I am not getting the walkbacks. Is there anything else loaded into your test image? I'd like to reproduce this and check if it's anything I did wrong in OSProcess.
My system looks like this:
$ Smalltalk version Squeak3.6alpha $ Smalltalk lastUpdateString latest update: #5179 $ Smalltalk vmVersion Squeak 3.2 of 11 July 2002 [latest update: #4917] $ uname -a Linux dtlewis 2.2.13 #14 Fri Dec 22 16:26:47 EST 2000 i686 unknown $ OSProcess versionInformation #('OSProcess version 3.0.3' 'CommandShell version 3.0' 'OSProcessPlugin: Squeak 3.2 of 11 July 2002 [latest update: #4917] with UnixOSProcessPlugin version 3.0.3 using concrete class UnixOSProcessPluginNoThisSessionAvailable, part of OSProcess version 3.0.3, running on linux-gnu unix VM with UnixOSProcessPlugin 4 July 2003 (e) plugin version 3.1 (plugin does not match class in image)') $
Dave
On Monday 07 July 2003 03:37 pm, David T. Lewis wrote:
I loaded the ContextCleanupDebugFix change set into an image with OSProcess installed, and I am not getting the walkbacks. Is there anything else loaded into your test image? I'd like to reproduce this and check if it's anything I did wrong in OSProcess.
Yes. My image is at update# 5331, with all of Anthony's context cleanup stuff loaded.
On Mon, Jul 07, 2003 at 04:59:08PM -0700, Ned Konz wrote:
On Monday 07 July 2003 03:37 pm, David T. Lewis wrote:
I loaded the ContextCleanupDebugFix change set into an image with OSProcess installed, and I am not getting the walkbacks. Is there anything else loaded into your test image? I'd like to reproduce this and check if it's anything I did wrong in OSProcess.
Yes. My image is at update# 5331, with all of Anthony's context cleanup stuff loaded.
OK, I see the same problem now. Thanks.
I notice that this fix also removed the return value of Process>>popTo: that is being used by the Decompiler. Is this part of the Decompiler code dead, or is this a problem?
Also, has anyone made progress on the problems between this and Process>>terminate?
< I'm a bug-fixing machine! >
This post brought to you by the BugFixArchiveViewer, a handy tool that makes it easy to comment on proposed fixes and enhancements for Squeak. For more information, check out the Web page for the BugFixArchiveViewer project: http://minnow.cc.gatech.edu/squeak/3214
< I'm a bug-fixing machine! >
debug the following expression using "debug it" in a text editor menu:
Morph new drawDropShadowOn: World assuredCanvas
through, through, send.
through, through, now "shadowColor" is highlighted.
I expect that one more "through" will highlight #shadowColor: but it does not.
Instead, it completes the entire block.
In fact, there doesn't seem to be any way to get into that second block.
For instance, step, step, through ought to get into that "during:" block, but doesn't.
< I'm a bug-fixing machine! >
This post brought to you by the BugFixArchiveViewer, a handy tool that makes it easy to comment on proposed fixes and enhancements for Squeak. For more information, check out the Web page for the BugFixArchiveViewer project: http://minnow.cc.gatech.edu/squeak/3214
< I'm a bug-fixing machine! >
On Monday 14 July 2003 04:13 pm, ned@bike-nomad.com wrote:
debug the following expression using "debug it" in a text editor menu:
Morph new drawDropShadowOn: World assuredCanvas
through, through, send.
through, through, now "shadowColor" is highlighted.
I expect that one more "through" will highlight #shadowColor: but it does not.
Instead, it completes the entire block.
In fact, there doesn't seem to be any way to get into that second block.
For instance, step, step, through ought to get into that "during:" block, but doesn't.
Can we do something about the broken debugger? I also notice that #popTo: has lost its return value.
Thanks,
squeak-dev@lists.squeakfoundation.org
-
Anthony Hannan -
David T. Lewis -
Ned Konz -
ned＠bike-nomad.com