11 comments

On 18-03-2004 16:21, Donald F. McLean wrote:

I have some votes available. Would anyone care to suggest a feature to
vote for?


Haha, nice! I just suggested some features in the plugins forum:

http://www.intellij.net/tracker/idea/viewSCR?publicId=15113
is one of them. Profiles for IDE settings - errors. Very handy if you
use the inspection gadgets plugin. Even more useful if you want to share
those settings with other developers.

Bas

0

A debugger that doesn't take 20 seconds to step over ArrayList list = new
ArrayList()?

A debugger that doesn't "skip" breakpoints that clearly should be executed
next (ie. a System.out.println)?

A debugger that doesn't take over 60 seconds to evaluate a HashMap's
contents? (or any Collection for that matter)

I am very close to giving up on using the debugger for all but the most
extreme circumstances and switching back to crude System.out.println()
statements or a logger or going back to 3.0. It's killing me to watch
Aurora struggle to evaluate an ArrayList with 5 entries in it. Hell, I had
the misfortune of inadvertantly clicking on the little plus sign of an
ArrayList of about 80 entries...poor Aurora locked up for about 5 minutes or
so.

4.0 is sweet. But the debugger has serious issues. Ironically, this
product is geared around the task of writing code...which often has to be
debugged. Until a new build comes out that addresses this, IDEA becomes a
glorified editor for me. I can still make use of the Generate Getters and
Setters. The refactoring is nice. Reformat Code is cool. I live by Ctrl-N
and Ctrl-Shift-N. And Inspect Code is quasi-orgasmic. But Lord help me if
I have a bug in my code...




"Bas Leijdekkers" <leijdekkers@no.spam.please.carp-technologies.nl> wrote in
message news:4059BFED.8040303@no.spam.please.carp-technologies.nl...

On 18-03-2004 16:21, Donald F. McLean wrote:

>

I have some votes available. Would anyone care to suggest a feature to
vote for?

>

Haha, nice! I just suggested some features in the plugins forum:

>

http://www.intellij.net/tracker/idea/viewSCR?publicId=15113
is one of them. Profiles for IDE settings - errors. Very handy if you
use the inspection gadgets plugin. Even more useful if you want to share
those settings with other developers.

>

Bas




0

I absolutely agree. It was going pretty sweet around build 1136 and
then it went bad again. Compared to Ariadna the debugging performance
is definitely worse.

I did post about this back then but nothing more came of it :
http://www.intellij.net/forums/thread.jsp?forum=22&thread=75862
: maybe we should submit an SCR? But then again I think I remember
reading that it was something to do with a debugger api change on the vm?

N.


Michael Morett wrote:

A debugger that doesn't take 20 seconds to step over ArrayList list = new
ArrayList()?

A debugger that doesn't "skip" breakpoints that clearly should be executed
next (ie. a System.out.println)?

A debugger that doesn't take over 60 seconds to evaluate a HashMap's
contents? (or any Collection for that matter)

I am very close to giving up on using the debugger for all but the most
extreme circumstances and switching back to crude System.out.println()
statements or a logger or going back to 3.0. It's killing me to watch
Aurora struggle to evaluate an ArrayList with 5 entries in it. Hell, I had
the misfortune of inadvertantly clicking on the little plus sign of an
ArrayList of about 80 entries...poor Aurora locked up for about 5 minutes or
so.

4.0 is sweet. But the debugger has serious issues. Ironically, this
product is geared around the task of writing code...which often has to be
debugged. Until a new build comes out that addresses this, IDEA becomes a
glorified editor for me. I can still make use of the Generate Getters and
Setters. The refactoring is nice. Reformat Code is cool. I live by Ctrl-N
and Ctrl-Shift-N. And Inspect Code is quasi-orgasmic. But Lord help me if
I have a bug in my code...




"Bas Leijdekkers" <leijdekkers@no.spam.please.carp-technologies.nl> wrote in
message news:4059BFED.8040303@no.spam.please.carp-technologies.nl...

>>On 18-03-2004 16:21, Donald F. McLean wrote:
>>
>>
>>>I have some votes available. Would anyone care to suggest a feature to
>>>vote for?
>>
>>Haha, nice! I just suggested some features in the plugins forum:
>>
>>http://www.intellij.net/tracker/idea/viewSCR?publicId=15113
>>is one of them. Profiles for IDE settings - errors. Very handy if you
>>use the inspection gadgets plugin. Even more useful if you want to share
>>those settings with other developers.
>>
>>Bas



0

What JVM do you use? Do you debug locally or remotely? 'Suspend All Threads While Stepping' is off?

0

To me - partly stuck with the Weblogic 6.1 - the following bug creates problems using WLS.

http://www.intellij.net/tracker/idea/viewSCR?publicId=23853

-


Trond

0

Should be 'using the WLS support in IntelliJ'

0

I'm using 1.3.1_06 on WLS 7.0 SP2. Debugging is done remotely thru sockets.
I dont use any Weblogic related support inside IDEA, quite frankly because I
haven't had time to experiment and get it to work. I start WLS outside of
IDEA and just connect to it remotely when I need to. I cant answer your
question about 'Suspend All Threads While Stepping' because I cant find that
setting. I checked IDE | Debugger and Run | Edit Configurations | Remote
and it's in neither location. Maybe it's shown in the debug window when I
am actually debugging, but right now I am not coding, so I dont have a way
to see that window.

You gave me an idea. I'll switch to 1.4.2_03 temporarily to see if that has
an effect. I noticed that "Force Classic VM for JDK 1.3 and earlier" in
IDE | Debugger was checked, but I am not sure of the effect of that setting.
I am also going to restructure my project to see if that has an effect. I
read in one of these threads that debugging weirdness seems to occur in
multi-module projects with dependencies between modules. I have two modules
and one is dependent on the other. Something inside me says this may be
part of the problem since the debugging slowness sort of appeared right
around the time of this new module redesign work a few months ago, but I
cant be sure. It's just a hunch. Modules are nice, but if they are
affecting debugging, I'll stick to a single module.

If I get good results, I'll post back to the community. Otherwise, assume I
am breaking into a nervous sweat whenever I have to step over a Collection.

M.


"Alexei Nikitin" <lex@intellij.com> wrote in message
news:16075826.1079699151417.JavaMail.itn@is.intellij.net...

What JVM do you use? Do you debug locally or remotely? 'Suspend All

Threads While Stepping' is off?
>


0

OK...I switched to 1.4.2_03, moved to a single module with two content roots
(vs. two modules with a dependency), cleared the IDEA cache and suddenly it
is snappy. The difference is dramatic. Collections of any size evaluate
immediately in the Debug window.

So was it a switch to 1.4.2_03 or the single module or clearing the cache
that fixed it? I dont know. I did it one at a time, but I was looking into
another problem which was still not fixed -- as I am stepping thru code one
line at a time, there is a particular point where F8 (step) acts like F9
(resume). It's pretty annoying and I still cant figure it out. Only after
a sigh of defeat did I think to go see how it responds to Collections and
noticed it resolved them instantly.

However, stepping over this line....

aResults.append(aBankAccount.getBankAccountId());

results in a Resume Program.

Yet, an Alt-F8 (evaluate) on aBankAccount.getBankAccountId() returns a 3
(Integer). aResults is just a StringBuffer so unless Sun broke the append
method, I dont think I need to question that. More importantly, this code
worked "as is" a few days ago. This class was not changed. There is a bug
somewhere due to other changes made elsewhere in the system, and I am trying
to track it down. If a do a CVS update/get clean copy, I can guaranteee
that this code will suddenly work again, but I dont want to do that. But
this is getting off topic.

I tried F7 to do that line a little bit at a time, but it still says
"Process resumed" on the status bar at the bottom. Very Very weird.

Hell, now it's not even just that line. I tried it again and it resumed on
the very first line...

BankAccountData aBankAccount = (BankAccountData) aIterator.next();

From here I would step and then see the false "Resume" on the line mentioned
earlier, but this time it just resumed from here. Arghhhh.

Anyways...for all those having problems with a slow debugger, try the steps
I mentioned above.


"Michael Morett" <michaelmorett@yahoo.com> wrote in message
news:c3fd5g$v68$1@is.intellij.net...

I'm using 1.3.1_06 on WLS 7.0 SP2. Debugging is done remotely thru

sockets.

I dont use any Weblogic related support inside IDEA, quite frankly because

I

haven't had time to experiment and get it to work. I start WLS outside of
IDEA and just connect to it remotely when I need to. I cant answer your
question about 'Suspend All Threads While Stepping' because I cant find

that

setting. I checked IDE | Debugger and Run | Edit Configurations | Remote
and it's in neither location. Maybe it's shown in the debug window when I
am actually debugging, but right now I am not coding, so I dont have a way
to see that window.

>

You gave me an idea. I'll switch to 1.4.2_03 temporarily to see if that

has

an effect. I noticed that "Force Classic VM for JDK 1.3 and earlier"

in

IDE | Debugger was checked, but I am not sure of the effect of that

setting.

I am also going to restructure my project to see if that has an effect. I
read in one of these threads that debugging weirdness seems to occur in
multi-module projects with dependencies between modules. I have two

modules

and one is dependent on the other. Something inside me says this may be
part of the problem since the debugging slowness sort of appeared right
around the time of this new module redesign work a few months ago, but I
cant be sure. It's just a hunch. Modules are nice, but if they are
affecting debugging, I'll stick to a single module.

>

If I get good results, I'll post back to the community. Otherwise, assume

I

am breaking into a nervous sweat whenever I have to step over a

Collection.
>

M.

>
>

"Alexei Nikitin" <lex@intellij.com> wrote in message
news:16075826.1079699151417.JavaMail.itn@is.intellij.net...

What JVM do you use? Do you debug locally or remotely? 'Suspend All

Threads While Stepping' is off?
>

>
>


0

So was it a switch to 1.4.2_03 or the single module or clearing the cache
that fixed it?


We use 1.4.2_03, more than 30 modules and it is fast enough. So maybe
the JRE is the reason?

Tom

0

If you haven't already used all your votes, this ER regarding JSP 2.0 features needs some votes ;)

http://www.intellij.net/tracker/idea/viewSCR?publicId=14990

0

You have my vote.

--
Norris Shelton
Sun Certified Java Programmer


"Ian Zabel" <ian@ezabel.com> wrote in message
news:33119216.1079969726852.JavaMail.itn@is.intellij.net...

If you haven't already used all your votes, this ER regarding JSP 2.0

features needs some votes ;)
>

http://www.intellij.net/tracker/idea/viewSCR?publicId=14990



0

Please sign in to leave a comment.