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

Breakpoints don't work in classes #2946

Closed
REAS opened this Issue Nov 14, 2014 · 4 comments

Comments

Projects
None yet
6 participants
@REAS
Member

REAS commented Nov 14, 2014

From the original post processing/processing-experimental#47

Breakpoints don't seem to work when placed within classes. If I create a breakpoint in a class the debugger never stops. For example, in the following code, if I place a breakpoint inside Ball.display the debugger won't stop (if I place it in the main draw function it does)

Ball b;

void setup()
{
  size(300, 300);
  b = new Ball(100, 100);
}


void draw()
{
  b.display();
}

class Ball
{
  int x, y;
  Ball(int _x, int _y)
  {
    this.x = _x;
    this.y = _y;
  }

  void display()
  {
    ellipse(x,y,20,20);
  }
}
@martinleopold

This comment has been minimized.

Show comment
Hide comment
@martinleopold

martinleopold Sep 30, 2015

Contributor

I have a fix for this in the old debug mode. Will send a pull request shortly.

Contributor

martinleopold commented Sep 30, 2015

I have a fix for this in the old debug mode. Will send a pull request shortly.

@Manindra29

This comment has been minimized.

Show comment
Hide comment
@Manindra29

Manindra29 Oct 1, 2015

Member

Hi Martin,

That would be great!

Thanks,
Manindra

On Wed, Sep 30, 2015 at 4:01 PM, Martin Leopold notifications@github.com
wrote:

I have a fix for this in the old debug mode. Will send a pull request
shortly.


Reply to this email directly or view it on GitHub
#2946 (comment)
.

Member

Manindra29 commented Oct 1, 2015

Hi Martin,

That would be great!

Thanks,
Manindra

On Wed, Sep 30, 2015 at 4:01 PM, Martin Leopold notifications@github.com
wrote:

I have a fix for this in the old debug mode. Will send a pull request
shortly.


Reply to this email directly or view it on GitHub
#2946 (comment)
.

@JoshDreamland

This comment has been minimized.

Show comment
Hide comment
@JoshDreamland

JoshDreamland Jan 29, 2017

This bug seems to have fallen between the cracks. It's really hard to debug something when your debugger suggests it isn't running. Anyway, what is breaking, here? Is Processing filtering breakpoints in classes it doesn't recognize, or is it failing to properly set a breakpoint in the generated source for nested classes, at all?

JoshDreamland commented Jan 29, 2017

This bug seems to have fallen between the cracks. It's really hard to debug something when your debugger suggests it isn't running. Anyway, what is breaking, here? Is Processing filtering breakpoints in classes it doesn't recognize, or is it failing to properly set a breakpoint in the generated source for nested classes, at all?

@pjm56

This comment has been minimized.

Show comment
Hide comment
@pjm56

pjm56 Apr 13, 2017

I can confirm this is definitely still an issue in 3.3.
A breakpoint on line 26 of the OP's code (the call to 'ellipse') never gets hit.
I can break at the display call, and "step in" to the class, but never break within a class.

pjm56 commented Apr 13, 2017

I can confirm this is definitely still an issue in 3.3.
A breakpoint on line 26 of the OP's code (the call to 'ellipse') never gets hit.
I can break at the display call, and "step in" to the class, but never break within a class.

JakubValtar added a commit to JakubValtar/processing that referenced this issue Apr 16, 2017

@benfry benfry closed this in #5008 Apr 17, 2017

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