Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Debug problems with the system.out.println statement
Debug problems with the system.out.println statement [message #145633] Thu, 26 February 2004 00:58 Go to next message
Eclipse UserFriend
Hi all...

i have been running eclipse on a windows 2000 box with no issues. Recently
i was debugging..the proble that i am facing is when i am stepping into
the code, if the debugger runs into a 'System.out.println("debug the
debugger");'i get a source not found error..and an option to change the
source.
What do i need to attach so that it works properly.
Re: Debug problems with the system.out.println statement [message #145650 is a reply to message #145633] Thu, 26 February 2004 03:20 Go to previous messageGo to next message
Eclipse UserFriend
Further to my first post...the problem is with loading
java.lang.ClassLoader.loadclass...how do i make the debugger load this
class, so that it can use the System.out.println statement without
reporting an error

exquisitus wrote:

> Hi all...

> i have been running eclipse on a windows 2000 box with no issues. Recently
> i was debugging..the proble that i am facing is when i am stepping into
> the code, if the debugger runs into a 'System.out.println("debug the
> debugger");'i get a source not found error..and an option to change the
> source.
> What do i need to attach so that it works properly.
Re: Debug problems with the system.out.println statement [message #145694 is a reply to message #145650] Thu, 26 February 2004 09:19 Go to previous messageGo to next message
Eclipse UserFriend
Do you have source attached to your JRE's class libraries? Source should be
found for the ClassLoader class in this case.

The first time you step into a "println", it may cause some class loading -
which it sounds like you are seeing. By pressing "step return" when this
happens, and then "step into" again, you should be able to get around the
class loading.

Darin

"Exquisitus" <foo@bar.com> wrote in message news:c1ka81$35r$1@eclipse.org...
> Further to my first post...the problem is with loading
> java.lang.ClassLoader.loadclass...how do i make the debugger load this
> class, so that it can use the System.out.println statement without
> reporting an error
>
> exquisitus wrote:
>
> > Hi all...
>
> > i have been running eclipse on a windows 2000 box with no issues.
Recently
> > i was debugging..the proble that i am facing is when i am stepping into
> > the code, if the debugger runs into a 'System.out.println("debug the
> > debugger");'i get a source not found error..and an option to change the
> > source.
> > What do i need to attach so that it works properly.
>
>
Re: Debug problems with the system.out.println statement [message #145881 is a reply to message #145694] Thu, 26 February 2004 17:38 Go to previous messageGo to next message
Eclipse UserFriend
Thanks for that Darin....arent the surces in a jar file?? Where do i get
the sources from? Pressing "step return" is a like a half fix. Imagine if
that that println is ina for loop ...il be "step return"...ing all the
time. Anyways lemme knwo yer views.
Thanks once again.

Darin Wright wrote:

> Do you have source attached to your JRE's class libraries? Source should be
> found for the ClassLoader class in this case.

> The first time you step into a "println", it may cause some class loading -
> which it sounds like you are seeing. By pressing "step return" when this
> happens, and then "step into" again, you should be able to get around the
> class loading.

> Darin

> "Exquisitus" <foo@bar.com> wrote in message news:c1ka81$35r$1@eclipse.org...
> > Further to my first post...the problem is with loading
> > java.lang.ClassLoader.loadclass...how do i make the debugger load this
> > class, so that it can use the System.out.println statement without
> > reporting an error
> >
> > exquisitus wrote:
> >
> > > Hi all...
> >
> > > i have been running eclipse on a windows 2000 box with no issues.
> Recently
> > > i was debugging..the proble that i am facing is when i am stepping into
> > > the code, if the debugger runs into a 'System.out.println("debug the
> > > debugger");'i get a source not found error..and an option to change the
> > > source.
> > > What do i need to attach so that it works properly.
> >
> >
Re: Debug problems with the system.out.println statement [message #146006 is a reply to message #145881] Fri, 27 February 2004 09:22 Go to previous messageGo to next message
Eclipse UserFriend
Sources are not usually in the jar file - they are usually in a seperate
"src.zip" that comes with a JDK. As well, source is not provided for all the
classes in the system libraries. Class loading should not happen on every
iteration through the loop - it should only happen the first time a class is
loaded (unless you are in a class loading loop :-)

Darin

"exquisitus" <foo@bar.com> wrote in message news:c1lsgm$bq2$1@eclipse.org...
> Thanks for that Darin....arent the surces in a jar file?? Where do i get
> the sources from? Pressing "step return" is a like a half fix. Imagine if
> that that println is ina for loop ...il be "step return"...ing all the
> time. Anyways lemme knwo yer views.
> Thanks once again.
>
> Darin Wright wrote:
>
> > Do you have source attached to your JRE's class libraries? Source should
be
> > found for the ClassLoader class in this case.
>
> > The first time you step into a "println", it may cause some class
loading -
> > which it sounds like you are seeing. By pressing "step return" when this
> > happens, and then "step into" again, you should be able to get around
the
> > class loading.
>
> > Darin
>
> > "Exquisitus" <foo@bar.com> wrote in message
news:c1ka81$35r$1@eclipse.org...
> > > Further to my first post...the problem is with loading
> > > java.lang.ClassLoader.loadclass...how do i make the debugger load this
> > > class, so that it can use the System.out.println statement without
> > > reporting an error
> > >
> > > exquisitus wrote:
> > >
> > > > Hi all...
> > >
> > > > i have been running eclipse on a windows 2000 box with no issues.
> > Recently
> > > > i was debugging..the proble that i am facing is when i am stepping
into
> > > > the code, if the debugger runs into a 'System.out.println("debug the
> > > > debugger");'i get a source not found error..and an option to change
the
> > > > source.
> > > > What do i need to attach so that it works properly.
> > >
> > >
>
>
Re: Debug problems with the system.out.println statement [message #146027 is a reply to message #146006] Fri, 27 February 2004 10:12 Go to previous messageGo to next message
Eclipse UserFriend
yep..i figured out the src bit. I inflated the src.zip just to see if
somethig happens. I just installed eclipse in a linux platform(the attach
source problem upon hitting a System.out.println isnt
happening)....however, it still runs to the java.lang classes and goes
through instantiating every bit of code..
heres an example
int zz=0;
for(int i=0;i<3;i++)
System.out.println(" All the class loading drama goes on and on for a
while here, till i use ctrl+return a number of times to go to the next
line");
zz=1;
Is this the expected behaviour?


Darin Wright wrote:

> Sources are not usually in the jar file - they are usually in a seperate
> "src.zip" that comes with a JDK. As well, source is not provided for all the
> classes in the system libraries. Class loading should not happen on every
> iteration through the loop - it should only happen the first time a class is
> loaded (unless you are in a class loading loop :-)

> Darin

> "exquisitus" <foo@bar.com> wrote in message news:c1lsgm$bq2$1@eclipse.org...
> > Thanks for that Darin....arent the surces in a jar file?? Where do i get
> > the sources from? Pressing "step return" is a like a half fix. Imagine if
> > that that println is ina for loop ...il be "step return"...ing all the
> > time. Anyways lemme knwo yer views.
> > Thanks once again.
> >
> > Darin Wright wrote:
> >
> > > Do you have source attached to your JRE's class libraries? Source should
> be
> > > found for the ClassLoader class in this case.
> >
> > > The first time you step into a "println", it may cause some class
> loading -
> > > which it sounds like you are seeing. By pressing "step return" when this
> > > happens, and then "step into" again, you should be able to get around
> the
> > > class loading.
> >
> > > Darin
> >
> > > "Exquisitus" <foo@bar.com> wrote in message
> news:c1ka81$35r$1@eclipse.org...
> > > > Further to my first post...the problem is with loading
> > > > java.lang.ClassLoader.loadclass...how do i make the debugger load this
> > > > class, so that it can use the System.out.println statement without
> > > > reporting an error
> > > >
> > > > exquisitus wrote:
> > > >
> > > > > Hi all...
> > > >
> > > > > i have been running eclipse on a windows 2000 box with no issues.
> > > Recently
> > > > > i was debugging..the proble that i am facing is when i am stepping
> into
> > > > > the code, if the debugger runs into a 'System.out.println("debug the
> > > > > debugger");'i get a source not found error..and an option to change
> the
> > > > > source.
> > > > > What do i need to attach so that it works properly.
> > > >
> > > >
> >
> >
Re: Debug problems with the system.out.println statement [message #146524 is a reply to message #146027] Mon, 01 March 2004 09:24 Go to previous messageGo to next message
Eclipse UserFriend
Have you tried adding a "Step Filter" from the Java > Debug > Step Filters
pref page?

Darin

"exquisitus" <foo@bar.com> wrote in message news:c1nmpf$go6$1@eclipse.org...
> yep..i figured out the src bit. I inflated the src.zip just to see if
> somethig happens. I just installed eclipse in a linux platform(the attach
> source problem upon hitting a System.out.println isnt
> happening)....however, it still runs to the java.lang classes and goes
> through instantiating every bit of code..
> heres an example
> int zz=0;
> for(int i=0;i<3;i++)
> System.out.println(" All the class loading drama goes on and on for a
> while here, till i use ctrl+return a number of times to go to the next
> line");
> zz=1;
> Is this the expected behaviour?
>
>
> Darin Wright wrote:
>
> > Sources are not usually in the jar file - they are usually in a seperate
> > "src.zip" that comes with a JDK. As well, source is not provided for all
the
> > classes in the system libraries. Class loading should not happen on
every
> > iteration through the loop - it should only happen the first time a
class is
> > loaded (unless you are in a class loading loop :-)
>
> > Darin
>
> > "exquisitus" <foo@bar.com> wrote in message
news:c1lsgm$bq2$1@eclipse.org...
> > > Thanks for that Darin....arent the surces in a jar file?? Where do i
get
> > > the sources from? Pressing "step return" is a like a half fix. Imagine
if
> > > that that println is ina for loop ...il be "step return"...ing all
the
> > > time. Anyways lemme knwo yer views.
> > > Thanks once again.
> > >
> > > Darin Wright wrote:
> > >
> > > > Do you have source attached to your JRE's class libraries? Source
should
> > be
> > > > found for the ClassLoader class in this case.
> > >
> > > > The first time you step into a "println", it may cause some class
> > loading -
> > > > which it sounds like you are seeing. By pressing "step return" when
this
> > > > happens, and then "step into" again, you should be able to get
around
> > the
> > > > class loading.
> > >
> > > > Darin
> > >
> > > > "Exquisitus" <foo@bar.com> wrote in message
> > news:c1ka81$35r$1@eclipse.org...
> > > > > Further to my first post...the problem is with loading
> > > > > java.lang.ClassLoader.loadclass...how do i make the debugger load
this
> > > > > class, so that it can use the System.out.println statement without
> > > > > reporting an error
> > > > >
> > > > > exquisitus wrote:
> > > > >
> > > > > > Hi all...
> > > > >
> > > > > > i have been running eclipse on a windows 2000 box with no
issues.
> > > > Recently
> > > > > > i was debugging..the proble that i am facing is when i am
stepping
> > into
> > > > > > the code, if the debugger runs into a 'System.out.println("debug
the
> > > > > > debugger");'i get a source not found error..and an option to
change
> > the
> > > > > > source.
> > > > > > What do i need to attach so that it works properly.
> > > > >
> > > > >
> > >
> > >
>
>
Re: Debug problems with the system.out.println statement [message #147372 is a reply to message #146524] Thu, 04 March 2004 18:35 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: foo.dog.com

yeah...i did try the step filter...same result.
Darin Wright wrote:

> Have you tried adding a "Step Filter" from the Java > Debug > Step Filters
> pref page?

> Darin

> "exquisitus" <foo@bar.com> wrote in message news:c1nmpf$go6$1@eclipse.org...
> > yep..i figured out the src bit. I inflated the src.zip just to see if
> > somethig happens. I just installed eclipse in a linux platform(the attach
> > source problem upon hitting a System.out.println isnt
> > happening)....however, it still runs to the java.lang classes and goes
> > through instantiating every bit of code..
> > heres an example
> > int zz=0;
> > for(int i=0;i<3;i++)
> > System.out.println(" All the class loading drama goes on and on for a
> > while here, till i use ctrl+return a number of times to go to the next
> > line");
> > zz=1;
> > Is this the expected behaviour?
> >
> >
> > Darin Wright wrote:
> >
> > > Sources are not usually in the jar file - they are usually in a seperate
> > > "src.zip" that comes with a JDK. As well, source is not provided for all
> the
> > > classes in the system libraries. Class loading should not happen on
> every
> > > iteration through the loop - it should only happen the first time a
> class is
> > > loaded (unless you are in a class loading loop :-)
> >
> > > Darin
> >
> > > "exquisitus" <foo@bar.com> wrote in message
> news:c1lsgm$bq2$1@eclipse.org...
> > > > Thanks for that Darin....arent the surces in a jar file?? Where do i
> get
> > > > the sources from? Pressing "step return" is a like a half fix. Imagine
> if
> > > > that that println is ina for loop ...il be "step return"...ing all
> the
> > > > time. Anyways lemme knwo yer views.
> > > > Thanks once again.
> > > >
> > > > Darin Wright wrote:
> > > >
> > > > > Do you have source attached to your JRE's class libraries? Source
> should
> > > be
> > > > > found for the ClassLoader class in this case.
> > > >
> > > > > The first time you step into a "println", it may cause some class
> > > loading -
> > > > > which it sounds like you are seeing. By pressing "step return" when
> this
> > > > > happens, and then "step into" again, you should be able to get
> around
> > > the
> > > > > class loading.
> > > >
> > > > > Darin
> > > >
> > > > > "Exquisitus" <foo@bar.com> wrote in message
> > > news:c1ka81$35r$1@eclipse.org...
> > > > > > Further to my first post...the problem is with loading
> > > > > > java.lang.ClassLoader.loadclass...how do i make the debugger load
> this
> > > > > > class, so that it can use the System.out.println statement without
> > > > > > reporting an error
> > > > > >
> > > > > > exquisitus wrote:
> > > > > >
> > > > > > > Hi all...
> > > > > >
> > > > > > > i have been running eclipse on a windows 2000 box with no
> issues.
> > > > > Recently
> > > > > > > i was debugging..the proble that i am facing is when i am
> stepping
> > > into
> > > > > > > the code, if the debugger runs into a 'System.out.println("debug
> the
> > > > > > > debugger");'i get a source not found error..and an option to
> change
> > > the
> > > > > > > source.
> > > > > > > What do i need to attach so that it works properly.
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >
Re: Debug problems with the system.out.println statement [message #147486 is a reply to message #147372] Fri, 05 March 2004 10:54 Go to previous message
Eclipse UserFriend
I suggest filing a bug report with a simple test case to demonstrate the
problem. I'm developing on XP, so I may not be able to reproduce the problem
(and I'm having a hard time understanding what the problem is, from the
description provided).

Darin

"exquisitus" <foo@dog.com> wrote in message news:c28eg1$vat$1@eclipse.org...
> yeah...i did try the step filter...same result.
> Darin Wright wrote:
>
> > Have you tried adding a "Step Filter" from the Java > Debug > Step
Filters
> > pref page?
>
> > Darin
>
> > "exquisitus" <foo@bar.com> wrote in message
news:c1nmpf$go6$1@eclipse.org...
> > > yep..i figured out the src bit. I inflated the src.zip just to see if
> > > somethig happens. I just installed eclipse in a linux platform(the
attach
> > > source problem upon hitting a System.out.println isnt
> > > happening)....however, it still runs to the java.lang classes and goes
> > > through instantiating every bit of code..
> > > heres an example
> > > int zz=0;
> > > for(int i=0;i<3;i++)
> > > System.out.println(" All the class loading drama goes on and on for a
> > > while here, till i use ctrl+return a number of times to go to the next
> > > line");
> > > zz=1;
> > > Is this the expected behaviour?
> > >
> > >
> > > Darin Wright wrote:
> > >
> > > > Sources are not usually in the jar file - they are usually in a
seperate
> > > > "src.zip" that comes with a JDK. As well, source is not provided for
all
> > the
> > > > classes in the system libraries. Class loading should not happen on
> > every
> > > > iteration through the loop - it should only happen the first time a
> > class is
> > > > loaded (unless you are in a class loading loop :-)
> > >
> > > > Darin
> > >
> > > > "exquisitus" <foo@bar.com> wrote in message
> > news:c1lsgm$bq2$1@eclipse.org...
> > > > > Thanks for that Darin....arent the surces in a jar file?? Where do
i
> > get
> > > > > the sources from? Pressing "step return" is a like a half fix.
Imagine
> > if
> > > > > that that println is ina for loop ...il be "step return"...ing
all
> > the
> > > > > time. Anyways lemme knwo yer views.
> > > > > Thanks once again.
> > > > >
> > > > > Darin Wright wrote:
> > > > >
> > > > > > Do you have source attached to your JRE's class libraries?
Source
> > should
> > > > be
> > > > > > found for the ClassLoader class in this case.
> > > > >
> > > > > > The first time you step into a "println", it may cause some
class
> > > > loading -
> > > > > > which it sounds like you are seeing. By pressing "step return"
when
> > this
> > > > > > happens, and then "step into" again, you should be able to get
> > around
> > > > the
> > > > > > class loading.
> > > > >
> > > > > > Darin
> > > > >
> > > > > > "Exquisitus" <foo@bar.com> wrote in message
> > > > news:c1ka81$35r$1@eclipse.org...
> > > > > > > Further to my first post...the problem is with loading
> > > > > > > java.lang.ClassLoader.loadclass...how do i make the debugger
load
> > this
> > > > > > > class, so that it can use the System.out.println statement
without
> > > > > > > reporting an error
> > > > > > >
> > > > > > > exquisitus wrote:
> > > > > > >
> > > > > > > > Hi all...
> > > > > > >
> > > > > > > > i have been running eclipse on a windows 2000 box with no
> > issues.
> > > > > > Recently
> > > > > > > > i was debugging..the proble that i am facing is when i am
> > stepping
> > > > into
> > > > > > > > the code, if the debugger runs into a
'System.out.println("debug
> > the
> > > > > > > > debugger");'i get a source not found error..and an option to
> > change
> > > > the
> > > > > > > > source.
> > > > > > > > What do i need to attach so that it works properly.
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>
>
Previous Topic:Import question
Next Topic:Question about Cyclic buildpath...
Goto Forum:
  


Current Time: Wed May 07 17:15:05 EDT 2025

Powered by FUDForum. Page generated in 0.05663 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top