> I tried to run a helloworld app without the monitoring piece. So the
> only thing I had was the addition of the modified Object class. I up'd
[quoted text clipped - 18 lines]
>
> thanks again for the feedback
> > I tried to run a helloworld app without the monitoring piece. So the
> > only thing I had was the addition of the modified Object class. I up'd
[quoted text clipped - 24 lines]
>
> robert
>>and if it does not prevent execution of itself for those
> objects then indeed you may have an endless recursion
my thought exactly. I would love to find someone who has actually gone
through some of these excercises.there are no corrections reported by
the author.
Oh well, on to the next problem
thanks for the help
Robert Klemme - 26 Sep 2006 12:29 GMT
>> I don't know what that piece of code does but if it creates objects for
>> monitoring and if it does not prevent execution of itself for those
[quoted text clipped - 6 lines]
> through some of these excercises.there are no corrections reported by
> the author.
Well, you might be able to detect this situation in the debugger if you
set a breakpoint on that StackOverflowError. If that does not help you
could print out the current stack trace every time you enter Object's
constructor.
Kind regards
robert
coltrane - 26 Sep 2006 18:24 GMT
> >> I don't know what that piece of code does but if it creates objects for
> >> monitoring and if it does not prevent execution of itself for those
[quoted text clipped - 15 lines]
>
> robert
Well, from what I have seen I do not believe that the jvm likes having
the Object constructor defined. If I attempt to output anything in that
construct I get a stack error before I can debug it. If the constructor
is empty there is no problem. Once I try to use an object I get the
error. which seems to make sense in a way. I hate to give up on a
problem but I think I must move on.
thanks again for everyone's help
cheers