This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 49540 - [40cat] green arrow designating line is gone
Summary: [40cat] green arrow designating line is gone
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-09-24 21:00 UTC by jasondonmoyer
Modified: 2006-03-24 10:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (113.89 KB, image/png)
2004-09-27 15:25 UTC, jasondonmoyer
Details
thread dump (10.41 KB, text/plain)
2004-09-27 15:25 UTC, jasondonmoyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jasondonmoyer 2004-09-24 21:00:56 UTC
[ BUILD # : 200409221800 ]
[ JDK VERSION : J2SE 1.5.0 ]

When I execute the debugger for my project, the
green arrow that used to designate the current
line is gone.  The cursor moves from line to line,
but I think the green arrow was much better from a
human factors standpoint.
Comment 1 _ lcincura 2004-09-27 15:02:28 UTC
More details from reporter:

The program counter is usually there after starting the debugger for
the first time and then something occurs which causes it to disappear
(and I've noticed recently other annotations, like the symbol denoting
an overriden method disappear as well... Strangely enough, my
breakpoint annotations remain).  Both the green arrow icon and the
highlighting disappear.  All annotations reappear when stopping the
debugger.

In all cases that I've seen this, the typical case is as follows:

1.  I hit a breakpoint in my code.
2.  I do some combination of step over, step into and continue
3.  Eventually the annotations disappear.  I've seen this as a result
of a continue (followed by doing something in my web app which causes
another breakpoint to be hit), step over and step into action

This occurs with a clean user directory.
Comment 2 _ lcincura 2004-09-27 15:12:56 UTC
One additional item of note (from reporter):

I only started seeing this behavior after upgrading to build
200409221800.  It wasn't happening in prior Q-builds (not sure about
the daily's between the last Q-Build and the daily build that I'm
using).  The behavior also seems to eventually occur during every
debugger session.
Comment 3 jasondonmoyer 2004-09-27 15:24:54 UTC
This behavior is actually fairly reproducible for me.  Additionally, I
don't lose all annotations each time I lose the program counter.  I'm
going to attach a screenshot and thread dump.
Comment 4 jasondonmoyer 2004-09-27 15:25:22 UTC
Created attachment 17890 [details]
screenshot
Comment 5 jasondonmoyer 2004-09-27 15:25:41 UTC
Created attachment 17891 [details]
thread dump
Comment 6 Jan Jancura 2004-09-29 09:51:19 UTC
I can not reproduce this behaviour niether on Java Project nor on Web one.
Can you attach some example application and describe how to reproduce
it, please?
And whats wxactly wrong? Green arrow only or green line too?
Is it reproducible on Web Project only?
Comment 7 jasondonmoyer 2004-09-29 15:24:08 UTC
This happens consistently on two of my web projects built from
existing ant scripts using the JPDA debugger.  As I've mentioned
before, it happens everytime based on my description and both the
green arrow and green line (and sometimes other annotations)
disappear.  It's continuing to occur with the latest daily build
(200409270901) as well.  I'll try creating an example project that
exhibits this behavior.
Comment 8 _ lcincura 2004-10-07 14:54:05 UTC
Reproducible in build 200410070525.

Steps to reproduce:
1, Open JPDA debugger project
2, Set breakpoint in StartActionProvider:doAction()
3, Attach with debugger to other netbeans instance
4, Start debugging of any project in the debugged instance
5, If you see the arrow, invoke step into/step over/step out in random
order and finally invoke continue
6, Start another debugging session in the debugged instance
7, Repeat from step 5
After few attempts you will reproduce it.

BTW I did not loose any other annotations, just the program cunter
highliting was not visible. Carret was not moved when step actions
were performed. When program counter was in another file, the file was
not opened.
Comment 9 dolly 2004-10-08 14:27:55 UTC
fixed in trunk:

We have listened on CURRENT_CALL_STACK changes in place of
CURRENT_THREAD changes. I do not understand *exactly* what was wrong,
but it works now.

QA: Test F7,8, Out on different sources.

Changed classes:
CurrentThreadAnnotationListener
Comment 10 Max Sauer 2005-07-11 08:52:20 UTC
verified in nbdev200507061800.