| Strange JDT debugger behavior [message #300087] |
Wed, 01 March 2006 14:28  |
Eclipse User |
|
|
|
I started to work with M5 and ran into weird JDT debugger behavior. I
set breakpoint, then launch Run-Time environment. It correctly stops on
my breakpoint, stays suspended for a while, then all of a sudden, it
resumes. It does not happen always, but this morning I've had it several
times. As long as I cannot provide sample code to reproduce this
problem, I wouldn't open report in Bugzilla. Nevertheless, maybe this
information could be useful to somebody.
|
|
|
|
|
|
| Re: Strange JDT debugger behavior [message #300118 is a reply to message #300092] |
Thu, 02 March 2006 10:08  |
| Eclipse User |
|
|
|
That's a main problem :-( I'm working on a large Eclipse-based project,
I'm absolutely not sure that I can extract small piece of code from it
to reproduce the problem. That's why I've not submitted a bug report
yet. But it happens very often for me. Last time I've finally got a
dialog that contained a bunch of messages about asynchronous view
errors. It seems to me that the using of the new asynchronous views is
the root of the problem, or at least it is a good indicator of some
other problem.
Kevin Barnes wrote:
> Alex Chapiro wrote:
>> Sorry, a little bit more information. This is definitely visualization
>> problem. The thread exists in suspended state, it just ended up
>> invisible in the Debug view. Selection of the Main thread enables
>> Resume button and I can really resume process.
>
>
> If this is a reproducible problem, I'd suggest you file a bug against
> Platform-Debug. There has been a lot of work on the the Debug Views in
> the last year (resulting in altogether new viewers).
> Kevin
|
|
|
Powered by
FUDForum. Page generated in 0.02439 seconds
Home