Home » Language IDEs » Java Development Tools (JDT) » debugging/breakpoint problem
| debugging/breakpoint problem [message #87879] |
Thu, 21 August 2003 13:58  |
Eclipse User |
|
|
|
Originally posted by: Keith.Wannamaker.org
I've got a problem with Eclipse 2.1.1 on NT 4Sp6a using Sun JDK 1.4.1.
The trouble is that Eclipse will no longer debug programs. By this I mean
that breakpoints will stop a running 'debug' program, but the GUI acts as
if the program is not paused. The thread windows says the VM is not
paused, yet the program is stopped at a breakpoint. Once Eclipse gets
into this state, it affects every project in my workspace. It happened to
me about three weeks ago, and I was forced to reinstall eclipse and
re-import my workspace. Once I did that, it worked fine again.
Yesterday, the debugging stopped working again. I don't see any bug
reports about this, so I suspect it is user error. Has anyone encountered
this? How did you overcome it?
Thanks,
Keith
|
|
| |
| Re: debugging/breakpoint problem [message #88003 is a reply to message #87910] |
Thu, 21 August 2003 16:52  |
| Eclipse User |
|
|
|
Originally posted by: maximgb.yandex.ru
On Thu, 21 Aug 2003 11:10:26 -0700, "Darin Swanson"
<Darin_Swanson@us.ibm.com> wrote:
Looks like I've got the same problem, the program stops at the
breakpoint but only resume/terminate commands available, stepping
commands disabled.
I use W2K SP3, JDK 1.4.2, Eclipse 2.1.1
Also I try to debug the WTK 1.1.4, 2.0 emulators with remote debug, on
70% cases the emulator crashes with
"zayit.exe - Application error
Instruction at address 0x00xxxxx tried to access memory at address
0x0000004
Memery couldn't be read" ( My translation, sorry if there are any
mistakes )
I have tried the JDK 1.4.1_03 results were exactly the same.
>Do you have the option to try debugging using a different JDK? (1.4.2 or
>ensure you have the latest 1.4.1)
>We saw weirdness with the earlier 1.4.1 VMs.
>HTH
>Darins
>
>"Keith Wannamaker" <Keith@Wannamaker.org> wrote in message
>news:bi317c$c7r$1@eclipse.org...
>> I've got a problem with Eclipse 2.1.1 on NT 4Sp6a using Sun JDK 1.4.1.
>> The trouble is that Eclipse will no longer debug programs. By this I mean
>> that breakpoints will stop a running 'debug' program, but the GUI acts as
>> if the program is not paused. The thread windows says the VM is not
>> paused, yet the program is stopped at a breakpoint. Once Eclipse gets
>> into this state, it affects every project in my workspace. It happened to
>> me about three weeks ago, and I was forced to reinstall eclipse and
>> re-import my workspace. Once I did that, it worked fine again.
>> Yesterday, the debugging stopped working again. I don't see any bug
>> reports about this, so I suspect it is user error. Has anyone encountered
>> this? How did you overcome it?
>>
>> Thanks,
>> Keith
>>
>
|
|
|
| Re: debugging/breakpoint problem [message #88015 is a reply to message #88003] |
Thu, 21 August 2003 17:13 |
| Eclipse User |
|
|
|
We have a bug report for the "zayit" problem.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36100
For the stepping problem, do you have the debug view visible with a "valid"
selection (stack frame, thread).
HTH
Darins
"Maxim Bazhenov" <maximgb@yandex.ru> wrote in message
news:qmbakvccqa3ijetm0n43p5cn8e472vt6oj@4ax.com...
> On Thu, 21 Aug 2003 11:10:26 -0700, "Darin Swanson"
> <Darin_Swanson@us.ibm.com> wrote:
>
> Looks like I've got the same problem, the program stops at the
> breakpoint but only resume/terminate commands available, stepping
> commands disabled.
> I use W2K SP3, JDK 1.4.2, Eclipse 2.1.1
> Also I try to debug the WTK 1.1.4, 2.0 emulators with remote debug, on
> 70% cases the emulator crashes with
> "zayit.exe - Application error
> Instruction at address 0x00xxxxx tried to access memory at address
> 0x0000004
> Memery couldn't be read" ( My translation, sorry if there are any
> mistakes )
> I have tried the JDK 1.4.1_03 results were exactly the same.
>
> >Do you have the option to try debugging using a different JDK? (1.4.2 or
> >ensure you have the latest 1.4.1)
> >We saw weirdness with the earlier 1.4.1 VMs.
> >HTH
> >Darins
> >
> >"Keith Wannamaker" <Keith@Wannamaker.org> wrote in message
> >news:bi317c$c7r$1@eclipse.org...
> >> I've got a problem with Eclipse 2.1.1 on NT 4Sp6a using Sun JDK 1.4.1.
> >> The trouble is that Eclipse will no longer debug programs. By this I
mean
> >> that breakpoints will stop a running 'debug' program, but the GUI acts
as
> >> if the program is not paused. The thread windows says the VM is not
> >> paused, yet the program is stopped at a breakpoint. Once Eclipse gets
> >> into this state, it affects every project in my workspace. It happened
to
> >> me about three weeks ago, and I was forced to reinstall eclipse and
> >> re-import my workspace. Once I did that, it worked fine again.
> >> Yesterday, the debugging stopped working again. I don't see any bug
> >> reports about this, so I suspect it is user error. Has anyone
encountered
> >> this? How did you overcome it?
> >>
> >> Thanks,
> >> Keith
> >>
> >
>
|
|
| | |
Goto Forum:
Current Time: Wed Jul 23 02:39:23 EDT 2025
Powered by FUDForum. Page generated in 0.05235 seconds |
Home