Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » [Debug] Off by one line problem in debugger (2.1)
[Debug] Off by one line problem in debugger (2.1) [message #67582] Mon, 09 June 2003 06:01 Go to next message
Eclipse UserFriend
Originally posted by: bob.objfac.com

In one particular class, the debugger steps and stops at the line
immediately preceding code line, e.g., on blank lines or comments above
code. It appears to happen only in this one class.

The appearance is what one would expect if debugging a class that does not
correspond to the source, but class is built from source and I have done a
Rebuild All.

Any idea how to stop this from happening?

Bob
Re: [Debug] Off by one line problem in debugger (2.1) [message #67631 is a reply to message #67582] Mon, 09 June 2003 07:09 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: bob.objfac.com

Once again I learn, if it looks like a duck, it probably is a duck. Was
debugging another version of the class. I don't know quite how, but a plugin
is grabbing a version out of a Java application project to resolve to!
Moreover, I can't make it stop. Even though there is an explicit dependency
in plugin.xml to the correct (plugin) project and this project is checked in
the build dependency list (and the incorrect project is not), when I debug a
breakpoint in the wrong project gets hit.

To make matters worse, even though there is no visible dependency anywhere
on this application project, I can't close it or PDE won't launch! (I've
reported this bug several times, but it always gets closed "can't
reproduce".)

The only cure is to build a completely new workplace. Grrr.

Bob

"Bob Foster" <bob@objfac.com> wrote in message
news:bc174k$o51$1@rogue.oti.com...
> In one particular class, the debugger steps and stops at the line
> immediately preceding code line, e.g., on blank lines or comments above
> code. It appears to happen only in this one class.
>
> The appearance is what one would expect if debugging a class that does not
> correspond to the source, but class is built from source and I have done a
> Rebuild All.
>
> Any idea how to stop this from happening?
>
> Bob
>
>
Re: [Debug] Off by one line problem in debugger (2.1) [message #68285 is a reply to message #67631] Mon, 09 June 2003 18:43 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jared-eclipse.mn.rr.com

If you have a reproducible test case for the breakpoint issue, you should
file a bug against JDT Debug.

- Jared

Bob Foster wrote:

> To make matters worse, even though there is no visible dependency anywhere
> on this application project, I can't close it or PDE won't launch! (I've
> reported this bug several times, but it always gets closed "can't
> reproduce".)
Re: [Debug] Off by one line problem in debugger (2.1) [message #70466 is a reply to message #68285] Wed, 11 June 2003 06:47 Go to previous message
Eclipse UserFriend
Originally posted by: bob.objfac.com

"Jared Burns" <jared-eclipse@mn.rr.com> wrote in message
news:bc2kgb$pme$3@rogue.oti.com...
> If you have a reproducible test case for the breakpoint issue, you should
> file a bug against JDT Debug.

Sorry, got carried away whining. Nah, I can't think how to reproduce this,
short of sending you my projects. I think I'll pass.

Bob

> - Jared
>
> Bob Foster wrote:
>
> > To make matters worse, even though there is no visible dependency
anywhere
> > on this application project, I can't close it or PDE won't launch! (I've
> > reported this bug several times, but it always gets closed "can't
> > reproduce".)
Previous Topic:How to include classfiles without the package declaration in the runtime classpath..
Next Topic:How to programatically select an Item in a TreeViewer
Goto Forum:
  


Current Time: Sat Aug 17 22:27:03 GMT 2024

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

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

Back to the top