Breakpoint weirdness in 3022

Since upgrading to 3022, I noticed that my breakpoints were getting a
proper "check" mark when I initially started debugging, but were almost
immediately changing to an X. I tried rebuilding my project, clearing
the classes dir, moving the output classes dir, checking and rechecking
the "Generate Debugging Info Box", but nothing worked. Finally, I was
able to fix things by - of all things - clearing the "Generate Debugging
Info" box and then trying to debug with a fresh classes dir. This
worked fine! I then re-enabled it and debugged, and it still works.
However, once I cleared the box AND cleared the classes cache, I finally
got the expected behavior.

This smells like a bug, but I wanted to post here mostly to help anyone
else with this problem.

adam

5 comments
Comment actions Permalink

I'm seeing this with part of my classes (incidentally this is the part
I'm working on.) We have a client and a server, I can run fine the
client in the debugger, but not the server. As you said, all my
breakpoints turn invalid as soon as I start the debugger.

Could you please post step by step how did you "fix" your problem?

tia,
Dimitar

Adam C wrote:

Since upgrading to 3022, I noticed that my breakpoints were getting a
proper "check" mark when I initially started debugging, but were almost
immediately changing to an X. I tried rebuilding my project, clearing
the classes dir, moving the output classes dir, checking and rechecking
the "Generate Debugging Info Box", but nothing worked. Finally, I was
able to fix things by - of all things - clearing the "Generate Debugging
Info" box and then trying to debug with a fresh classes dir. This
worked fine! I then re-enabled it and debugged, and it still works.
However, once I cleared the box AND cleared the classes cache, I finally
got the expected behavior.

This smells like a bug, but I wanted to post here mostly to help anyone
else with this problem.

adam

0
Comment actions Permalink

Sure, although I have had this happen again and it wasn't as easy to fix
this time. I just went through a loop of enabling/disabling the
"Generate Debugging Info", Rebuilding the project, and restarting IJ.
Eventually, it started working again. I wish I had a simpler approach,
but this is what worked for me. If I remember right, restarting was the
last thing I did before I got bps back.

hope that helps

adam

dimitar wrote:

I'm seeing this with part of my classes (incidentally this is the part
I'm working on.) We have a client and a server, I can run fine the
client in the debugger, but not the server. As you said, all my
breakpoints turn invalid as soon as I start the debugger.

Could you please post step by step how did you "fix" your problem?

tia,
Dimitar

Adam C wrote:

>> Since upgrading to 3022, I noticed that my breakpoints were getting a
>> proper "check" mark when I initially started debugging, but were
>> almost immediately changing to an X. I tried rebuilding my project,
>> clearing the classes dir, moving the output classes dir, checking and
>> rechecking the "Generate Debugging Info Box", but nothing worked.
>> Finally, I was able to fix things by - of all things - clearing the
>> "Generate Debugging Info" box and then trying to debug with a fresh
>> classes dir. This worked fine! I then re-enabled it and debugged,
>> and it still works. However, once I cleared the box AND cleared the
>> classes cache, I finally got the expected behavior.
>>
>> This smells like a bug, but I wanted to post here mostly to help
>> anyone else with this problem.
>>
>> adam

0
Comment actions Permalink

I keep having this problem, although I can't believe there are only two
of us. During the day, as I'm debugging, suddenly breakpoints get
disabled. If I hover on the X is says that the Source code has changed,
even though I'm sure it hasn't. Could this be because my source is on a
network drive? I would really love to find out why this is happening.

thanks,
adam

Adam C wrote:

Sure, although I have had this happen again and it wasn't as easy to fix
this time. I just went through a loop of enabling/disabling the
"Generate Debugging Info", Rebuilding the project, and restarting IJ.
Eventually, it started working again. I wish I had a simpler approach,
but this is what worked for me. If I remember right, restarting was the
last thing I did before I got bps back.

hope that helps

adam

dimitar wrote:

>> I'm seeing this with part of my classes (incidentally this is the part
>> I'm working on.) We have a client and a server, I can run fine the
>> client in the debugger, but not the server. As you said, all my
>> breakpoints turn invalid as soon as I start the debugger.
>>
>> Could you please post step by step how did you "fix" your problem?
>>
>> tia,
>> Dimitar
>>
>> Adam C wrote:
>>
>>> Since upgrading to 3022, I noticed that my breakpoints were getting a
>>> proper "check" mark when I initially started debugging, but were
>>> almost immediately changing to an X. I tried rebuilding my project,
>>> clearing the classes dir, moving the output classes dir, checking and
>>> rechecking the "Generate Debugging Info Box", but nothing worked.
>>> Finally, I was able to fix things by - of all things - clearing the
>>> "Generate Debugging Info" box and then trying to debug with a fresh
>>> classes dir. This worked fine! I then re-enabled it and debugged,
>>> and it still works. However, once I cleared the box AND cleared the
>>> classes cache, I finally got the expected behavior.
>>>
>>> This smells like a bug, but I wanted to post here mostly to help
>>> anyone else with this problem.
>>>
>>> adam

0
Comment actions Permalink

Adam C wrote:

I keep having this problem, although I can't believe there are only two
of us. During the day, as I'm debugging, suddenly breakpoints get
disabled. If I hover on the X is says that the Source code has changed,
even though I'm sure it hasn't. Could this be because my source is on a
network drive? I would really love to find out why this is happening.


My source is on the local drive and I used to get the same behaviour.
Then I went back to the official 4.5 release, which worked without a
hitch with the same caches, different config. Then, the other day I
started the EAP and it just worked.

Btw, I'm using JDK 1.3 for running and debugging.

Dimitar

0
Comment actions Permalink

Don't worry Adam. You two aren't the only ones seeing this problem. I've run into it myself. Breakpoints all of a sudden become "invalid" but begin working again after a series of opening new projects and shutting down IJ (don't know the exact steps required - it just starts working again).

Dustin

0

Please sign in to leave a comment.