Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WAPharoWalkback misuses debugger API #689

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Closed

WAPharoWalkback misuses debugger API #689

GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

WAPharoWalkback expects the following code to work:

Semaphore forMutualExclusion critical: [
    | sender |
    sender := thisContext sender.
    sender tempAt: sender tempScopedNames size ]

However this does not work with a Closure VM see:
http://lists.gforge.inria.fr/pipermail/pharo-project/2011-September/053729.html

Original issue reported on code.google.com by philippe...@gmail.com on 13 Sep 2011 at 8:02

@GoogleCodeExporter
Copy link
Author

Issue 650 has been merged into this issue.

Original comment by philippe...@gmail.com on 17 Sep 2011 at 9:35

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Even when using what is supposed to be the right API the code still breaks. So 
I'm dropping the temps from the walkback entirely. I added a test that will 
fail when they are fixed in Pharo. 'Full Stack' now works again in the walkback 
without raising an exception.

Name: Seaside-Pharo-Development-pmm.56
Author: pmm
Time: 17 September 2011, 11:44:43 am
UUID: 77b06897-256c-4262-94a7-30983883fe98
Ancestors: Seaside-Pharo-Development-pmm.55

- Issue 689:    WAPharoWalkback misuses debugger API
- drop temps because stack introspection is borken in Pharo

Name: Seaside-Tests-Pharo-Development-pmm.17
Author: pmm
Time: 17 September 2011, 11:45:50 am
UUID: 4df6cbec-6433-4672-818a-6f72c8f56c7d
Ancestors: Seaside-Tests-Pharo-Development-lr.16

- Issue 689:    WAPharoWalkback misuses debugger API
- test to detect when stack introspection is working again in Pharo

Original comment by philippe...@gmail.com on 17 Sep 2011 at 9:50

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant