search

dpo / atom-python-debugger

IDE-like Python debugger for Atom
MIT License
42 stars 13 forks source link

Use a different entry point feature? #13

Open davidde opened 7 years ago

davidde commented 7 years ago

I was wondering whether I am doing something wrong or this feature is not yet working properly.

I am trying to debug a script that is called by another file.

I already figured out the 'e=filename' should be entered in the debugger commands box after the debugger is started. But afterwards it just jumps to the start of that file, instead of to the breakpoint in the actual script.

Is this a known problem or should this just work? I'm on Linux Mint 18 if that matters.

Please keep up the good work! This is shaping up to be a wonderful debugger ...

dpo commented 7 years ago

Sorry time hasn't allowed me to care properly for this package lately. Did you remember to add the breakpoint before starting the debugger? If not, it's not taken into account (that's a current defect).

davidde commented 7 years ago

Yes, I added the breakpoint before starting.

I hear you. It can't be easy maintaining such a package in your spare time. I would help out, but my Javascript skills are very rudimentary, even more so for coffeescript & less.

Sorry I couldn't be of more help.

dpo commented 6 years ago

Breakpoints have improved now. A lot of time has gone by, but if you get a chance, please let me know if the same behavior persists.