Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Thread active only when debuggin in JDT(Java thread active only when debugging)
Thread active only when debuggin in JDT [message #779479] Sun, 15 January 2012 21:21 Go to next message
peluo uo is currently offline peluo uoFriend
Messages: 1
Registered: January 2012
Junior Member
Hi to everyone.

I'm working with JDT Indigo 20110916-0149, in OpenSuse 64 bits.

I have a program with a weird behaviour. It has a thread that only is active when I put a break point on it and debug in step by step mode. Free running or free debugging (without break points) does not work. Afther this break point is reached, the program runs as expected.

My first idea was a problem with thread interlocks, but the thing is that it is not really "stopped" it is active but only in step by step.

Any idea?

Thanks in advance.

[Updated on: Sun, 15 January 2012 21:22]

Report message to a moderator

Re: Thread active only whe debuggin in JDT [message #779486 is a reply to message #779479] Sun, 15 January 2012 21:47 Go to previous message
David Wegener is currently offline David WegenerFriend
Messages: 1445
Registered: July 2009
Senior Member
On 01/15/2012 03:21 PM, peluo uo wrote:
> Hi to everyone.
>
> I'm working with JDT Indigo 20110916-0149, in OpenSuse 64 bits.
>
> I have a program with a weird behaviour. It has a thread that only is
> active when I put a break point on it and debug in step by step mode.
> Free running or free debugging (without break points) does not work.
> Afther this break point is reached, the program runs as expected.
>
> My first idea was a problem with thread interlocks, but the thing is
> that it is not really "stopped" it is active but only in step by step.
>
> Any idea?
>
> Thanks in advance.
There are any number of reasons that this could be happening. Threads
are very susceptible to race conditions that can cause strange
behaviors. Adding breakpoints to the program completely changes the
thread interactions.

Some things that could be happening, thread trying to access variable
prior to initialization, exception being thrown because state isn't
correct, thread exiting prematurely, etc.

You haven't provided enough information or done enough debugging for us
to provide a more meaningful response.

Note that this is also doesn't seem to be an Eclipse related question,
but a more general Java development question. This forum is for
questions about the Eclipse Java Development tools not general Java
questions.
Previous Topic:While loop
Next Topic:Help needed for create jsp-servlet program..!!!
Goto Forum:
  


Current Time: Thu Apr 25 12:33:45 GMT 2024

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

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

Back to the top