Bug 559795

Summary:

InvalidStackFrameException <unknown receiving type> when using a conditional breakpoint

Product:

[Eclipse Project] JDT

Reporter:

james tomkinson <jamestomk>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

CC:

jamestomk, loskutov, mcoufal

Version:

4.14

Keywords:

needinfo

Target Milestone:

---

Hardware:

OS:

Windows 10

Whiteboard:

stalebug

Attachments:

Description	Flags
error message popup	none
screencap of the conditional breakpoint text referencing a method param class public var	none

Description james tomkinson

2020-02-03 13:04:48 EST

when I set a conditional that references a method parameter or local var set from a method parameter, I get a breakpoint error upon first evaluation:
  GUIControlledBackTest(TradingAlgoManager).addOHLCvToTA4jSeries(OHLCv) line: 1265	
  <unknown receiving type>(TradingAlgoManager).pushOHLCvToAlgos(OHLCv, boolean) line: 2131
  <unknown receiving type>...

this does not occur if I reference a class 
  
related screencaps will be added.

-- Configuration Details --
Product: Eclipse IDE 4.14.0.20191212-1200 (org.eclipse.epp.package.jee.product)Installed Features:
 org.eclipse.jdt 3.18.200.v20191210-0610
Versioning Plugin:
 org.eclipse.platform 4.14.0.v20191210-0610

Comment 1 james tomkinson

2020-02-03 13:06:11 EST

Created attachment 281687 [details]
error message popup

Comment 2 james tomkinson

2020-02-03 13:07:36 EST

Created attachment 281688 [details]
screencap of the conditional breakpoint text referencing a method param class public var

Comment 3 Andrey Loskutov

2020-02-03 13:40:32 EST

James, please try to reduce your code to something that still shows your original problem and attach here.

Comment 4 Eclipse Genie

2022-03-01 15:54:11 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Eclipse Genie

2024-02-27 00:15:15 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.