[#ROR-818] Display View (when debugging) complains about the stack frame and won't work under Eclipse 3.3 - ASAP

Aptana RadRails

Display View (when debugging) complains about the stack frame and won't work under Eclipse 3.3

Created: 28/Apr/08 12:08 PM Updated: 10/Mar/09 12:19 PM

Component/s:

Debugging

Affects Version/s:

1.0.1

Fix Version/s:

1.2.0

Issue Links:

Depends

This issue depends on:

~~STU-680~~ Use Eclipse 3.4 as the base platform

Impact on Workflow:	Major
Studio Install Type:	Eclipse Plugin
Operating System:	Ubuntu, Windows XP
Participants:	Chris Williams and javier

Description

« Hide

described in forum post

http://forums.aptana.com/viewtopic.php?t=5330

Whenever you try to evaluate the expression in the Display View, an error is displayed and nothing gets evaluated. The error message is:

Evaluation failed. Reason(s):
A stack frame must be selected to provide a context for an evaluation.

In the same computer (and rails project) it works fine on Eclipse 3.2 and fails in 3.3

All

Comments

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Chris Williams - 30/Apr/08 12:06 PM

Not sure if I can fix this in nay easy way as they changed the API after 3.2 and we're still targeting 3.2 as the Aptana base...

[ Permlink | « Hide ]

Chris Williams - 19/May/08 09:56 AM

For now I'm pushing to 1.2 of RadRails. I'm not sure which version we'll have a fix for this. The effective fix will be when we move to 3.3+ for the Aptana base and target that, or offer targeted versions of the plugins for those versions of Eclipse. We've discussed this extensively, but moving to 3.3 or 3.4 has been continually pushed off as lower priority. My gfuess is we'll be forced to pretty soon when 3.4 hits final.

[ Permlink | « Hide ]

Chris Williams - 18/Feb/09 03:37 PM

Fixed in 1.2.0 when used on Eclipse 3.4 or Studio 1.3+.

[ Permlink | « Hide ]

Chris Williams - 10/Mar/09 12:01 PM

Only tie things resolved in 1.1.2 and 1.2.0 to 1.1.2 as fixed version (since it's assumed that 1.2.0 as a later release will contain all the previous release's bugfixes).