[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools.jdt] Re: Error while debugging my MIDlet

Well, either way I finally figured out how to get the 3.1 and install it, 
updaing the workspace and all of that (I backed up the old one of course). 
I wasn't able to see if it actually fixed the problem because I ran into a 
bunch of problems trying to update the list of installed JRE's i wanted to 
use (1.5, 1.4, the three Nokias, etc).  I'd try to click on the "Installed 
JREs" tab in Prefs but it would give me a "Cound Not Accept Changes: the 
currently displayed page contains invalid values".  Sometimes I'd get that 
message just trying to open up Preferences.  After clicking around I'd 
manage to install the jre's, but when i'd close the window and come back 
they'd all be gone or the same "could not accept changes" error would occur. 
Not being able to install the jre's and the fact that the project was JRE 
system library was "unbound" made me hesistant to test any debugging tests. 
I searched the bug database but didn't find anything about this so I'll 
submit a bug with all the juicy error log details.
Thanks
Mike

"Darin Swanson" <Darin_Swanson@xxxxxxxxxx> wrote in message 
news:d7l2qc$8sg$1@xxxxxxxxxxxxxxxxxxx
> No... I think you misunderstood...or I was not clear. The bug is fixed in 
> the 3.1 stream NOT the 3.0.2 stream.
> It will not be fixed in the 3.0.2 stream
>
> No bug report is necessary unless you try with Eclipse 3.1 and the problem 
> still exists.
>
> HTH
> Darins
>
> "Mike ONeil" <moneil@xxxxxxxxxxxx> wrote in message 
> news:d7l25s$80i$1@xxxxxxxxxxxxxxxxxxx
>> Hahaha.  Very good, then I shall post the bug and all the gory error log 
>> details and absolve myself of noob guilt.
>> Thanx again, the bug will be posted shortly...
>> Mike
>>
>>
>>
>> "Darin Swanson" <Darin_Swanson@xxxxxxxxxx> wrote in message 
>> news:d7l1fh$6s5$1@xxxxxxxxxxxxxxxxxxx
>>> Any time you get an exception (especially an internal error) that is 
>>> dumped to the log we want to know about it...even if you are doing 
>>> something wrong...we should handle it gracefully and tell you how to fix 
>>> the problem :-)
>>>
>>> Searching using https://bugs.eclipse.org/bugs/query.cgi
>>> and entering
>>> org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getArgumentTypeNames(JDIStackFrame.java:324)
>>> as a comment to search for, I found:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=78605
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=88726
>>>
>>> The good news is that both problems are marked as fixed or working in 
>>> the Eclipse 3.1 stream.
>>> You could try Eclipse 3.1 RC1 or wait a couple more weeks for when 
>>> Eclipse 3.1 is released (but why wait :-) )
>>>
>>> HTH
>>> Darins
>>>
>>> "Mike ONeil" <moneil@xxxxxxxxxxxx> wrote in message 
>>> news:d7kmmq$nd8$1@xxxxxxxxxxxxxxxxxxx
>>>> Hello again.  Thanx for the tips, but I'm new to Eclipse and want to 
>>>> make sure I'm doing things properly before I start mentioning bugs.  I 
>>>> showed the Error Log, but all it said was the same
>>>> "An internal error occurred during: "Debug"."
>>>>
>>>> I expanded it though and got the whole stack, which is:
>>>>
>>>> java.lang.IllegalArgumentException
>>>> at 
>>>> org.eclipse.jdi.internal.GenericSignature.getArgumentsSignature(GenericSignature.java:65)
>>>> at 
>>>> org.eclipse.jdi.internal.MethodImpl.argumentTypeSignatures(MethodImpl.java:302)
>>>> at 
>>>> org.eclipse.jdi.internal.MethodImpl.argumentTypeNames(MethodImpl.java:278)
>>>> at 
>>>> org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getArgumentTypeNames(JDIStackFrame.java:324)
>>>> at 
>>>> org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getStackFrameText(JDIModelPresentation.java:1498)
>>>> at 
>>>> org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getText(JDIModelPresentation.java:204)
>>>> at 
>>>> org.eclipse.debug.internal.ui.LazyModelPresentation.getText(LazyModelPresentation.java:101)
>>>> at 
>>>> org.eclipse.debug.internal.ui.DelegatingModelPresentation.getText(DelegatingModelPresentation.java:158)
>>>> at 
>>>> org.eclipse.debug.internal.ui.views.DebugViewLabelDecorator$LabelJob.run(DebugViewLabelDecorator.java:326)
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>>>>
>>>> I dug around the bug database but didn't find anything, however I'm not 
>>>> certain on how to report this bug (if it is one).  For the sake of the 
>>>> poor bug chasers at Eclipse can ya give me any hints on how to go about 
>>>> this?
>>>> Thank you much.
>>>> Mike
>>>>
>>>>
>>>> "Darin Swanson" <Darin_Swanson@xxxxxxxxxx> wrote in message 
>>>> news:d7jae0$1e0$1@xxxxxxxxxxxxxxxxxxx
>>>>> Mike,
>>>>>
>>>>> Check the .log file for the full stack trace of the exception.
>>>>> Window>Show View>Other>PDE Runtime>Error Log
>>>>>
>>>>> Then search bugzilla to see if the problem is known.
>>>>> If not, report the problem
>>>>>
>>>>> Thanks
>>>>> Darins
>>>>>
>>>>> "Mike ONeil" <moneil@xxxxxxxxxxxx> wrote in message 
>>>>> news:d7j4gq$s7t$1@xxxxxxxxxxxxxxxxxxx
>>>>>> I'm using the Nokia SDK Plug-In to develop a game on a cell phone 
>>>>>> using Eclipse 3.0.2 using Windows XP.  Here's what happens:
>>>>>>
>>>>>> I can run the program fine, can run it in debug mode fine, however, 
>>>>>> when I set certain breakpoints, I get this error message:
>>>>>>
>>>>>> Debug (Error: An Internal error occurred during: "Debug",)
>>>>>> java.lang.illegalArgumentException
>>>>>> .
>>>>>> .
>>>>>> .
>>>>>>
>>>>>>
>>>>>> Seems to happen only when I put breakpoints in certain parts of the 
>>>>>> code, though I'm not sure what parts of the code cause it or not. 
>>>>>> Everything runs error free otherwise.  Has anyone else encountered 
>>>>>> this or know what it's about?
>>>>>>
>>>>>> Thanx
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>