Issue 1034 in moose-technology: Glamour easel and GTDebugger

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

Issue 1034 in moose-technology: Glamour easel and GTDebugger

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Critical

New issue 1034 by [hidden email]: Glamour easel and GTDebugger
http://code.google.com/p/moose-technology/issues/detail?id=1034

Hi!

I have spotted an important bug. If I enter the following in the Glamour  
Roassal easel:
view nodes: (1 to: 20).
self halt.

A debugger is open, but I cannot step in. Apparently the code source is not  
accessible. This is a major regression...


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1034 in moose-technology: Glamour easel and GTDebugger

moose-technology
Updates:
        Labels: Component-Glamour Milestone-5.0

Comment #1 on issue 1034 by [hidden email]: Glamour easel and  
GTDebugger
http://code.google.com/p/moose-technology/issues/detail?id=1034

This is not related to the debugger, but to the changes induced Opal. It  
seems that GLMDoItContext is not compliant anymore.

Can someone more knowledgeable take a look at this?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1034 in moose-technology: Glamour easel and GTDebugger

moose-technology

Comment #2 on issue 1034 by [hidden email]: Glamour easel and  
GTDebugger
http://code.google.com/p/moose-technology/issues/detail?id=1034

The problem appears because the code is compiled into a method without  
source code, and then when it's executed the source code seems to be  
needed. It can be solved by setting a notifier object when calling the  
compiler: in GLMRoassalEasel>>evaluate:in:for:

Smalltalk compiler
                        evaluate: script
                        in: context
                        to: context
                        notifying: self
                        ifFail: [^ #failedDoit]

Seems to work, but I'm not sure exactly what the notifier should do.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1034 in moose-technology: Glamour easel and GTDebugger

moose-technology

Comment #3 on issue 1034 by [hidden email]: Glamour easel and  
GTDebugger
http://code.google.com/p/moose-technology/issues/detail?id=1034

Added the fix to all other esels

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1034 in moose-technology: Glamour easel and GTDebugger

moose-technology

Comment #4 on issue 1034 by [hidden email]: Glamour easel and  
GTDebugger
http://code.google.com/p/moose-technology/issues/detail?id=1034

If I do in the Roassal Easel (or other ones):

view halt

I get this at the moment:

DoItIn: ThisContext
        ^ (ThisContext namedTempAt: 1) halt

Can we not get the actual source?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1034 in moose-technology: Glamour easel and GTDebugger

moose-technology
Updates:
        Status: Fixed

Comment #5 on issue 1034 by [hidden email]: Glamour easel and  
GTDebugger
https://code.google.com/p/moose-technology/issues/detail?id=1034

As far as I can tell, this is fixed now. Let me know if you still have  
problems in this area.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev