Issue 5146 in pharo: CodeHolder >> #decompiledSourceIntoContents not robust enough for handling unknown temps, making it impossible to debug certain methods

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

Issue 5146 in pharo: CodeHolder >> #decompiledSourceIntoContents not robust enough for handling unknown temps, making it impossible to debug certain methods

pharo
Status: New
Owner: ----
Labels: Milestone-1.3 Type-Bug

New issue 5146 by [hidden email]: CodeHolder >>  
#decompiledSourceIntoContents not robust enough for handling unknown temps,  
making it impossible to debug certain methods
http://code.google.com/p/pharo/issues/detail?id=5146

The code holder uses decompileWithTemps, which can fail.
In case of an error, I would fall back to the standard decompile instead.

Attachments:
        CodeHolder-decompiledSourceIntoContents.st  863 bytes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5146 in pharo: CodeHolder >> #decompiledSourceIntoContents not robust enough for handling unknown temps, making it impossible to debug certain methods

pharo

Comment #1 on issue 5146 by [hidden email]: CodeHolder >>  
#decompiledSourceIntoContents not robust enough for handling unknown temps,  
making it impossible to debug certain methods
http://code.google.com/p/pharo/issues/detail?id=5146

The decompiler itself does the same thing in #decompileBlock: aBlock. Also  
wrapped that with an [] ifError: [method decompile]

Attachments:
        Decompiler-decompileBlock.st  1.2 KB


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5146 in pharo: CodeHolder >> #decompiledSourceIntoContents not robust enough for handling unknown temps, making it impossible to debug certain methods

pharo
Updates:
        Status: FixToInclude
        Labels: Milestone-1.4

Comment #2 on issue 5146 by [hidden email]: CodeHolder >>  
#decompiledSourceIntoContents not robust enough for handling unknown temps,  
making it impossible to debug certain methods
http://code.google.com/p/pharo/issues/detail?id=5146

Thanks. I will integrate that.
BTW did you sign the licence?
BTW BTW what is an unknown tmp.




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5146 in pharo: CodeHolder >> #decompiledSourceIntoContents not robust enough for handling unknown temps, making it impossible to debug certain methods

pharo
Updates:
        Status: Closed
        Labels: -Milestone-1.3

Comment #3 on issue 5146 by [hidden email]: CodeHolder >>  
#decompiledSourceIntoContents not robust enough for handling unknown temps,  
making it impossible to debug certain methods
http://code.google.com/p/pharo/issues/detail?id=5146

in 14287


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker