Bug 414961 - Breakpoints set in pydev perspective are ignored during debugging
Summary: Breakpoints set in pydev perspective are ignored during debugging
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-pydev
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnston
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-12-06 22:30 UTC by Jesse Keating
Modified: 2013-01-10 02:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-11-06 21:33:59 UTC

Attachments (Terms of Use)

Description Jesse Keating 2007-12-06 22:30:13 UTC
I set a number of breakpoints in my sources in the pydev perspective.  But when
trying to debug they were completely ignored.  This was obviously confusing.

However breakpoints I set while in the debug perspective were seen.

Comment 1 Jeff Johnston 2008-02-12 19:44:48 UTC
Please retry with eclipse-pydev-1.3.12-1.fc8 which has updated the eclipse-pydev
release and contains a number of fixes.  The simple test below works for me:

--- simplestModule.py ---
def f(): pass
--- end simplestModule.py ---

--- simpleImport.py ---
import simplestModule as sm
--- end simpleImport.py ---

I set a breakpoint at the sm.f() line in simpleImport.py in the pydev editor.  I
debug with simpleImport.py as main module and I get my breakpoint.  I am then
able to step into simplestModule.py.  I do run into an error after stepping past
the last line into termination, but that is a separate problem.

If you have another scenario that is not working, please provide.

Comment 2 Bug Zapper 2008-05-14 04:06:42 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 3 Alexander Kurtakov 2008-11-06 21:33:59 UTC
No response for more then 6 months from the reporter. Pydev is now at version 1.3.24 which has many debugging improvements to the version Jeff asked to test.
Please reopen if there is still problem.

Note You need to log in before you can comment on or make changes to this bug.