|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #53702] GUI editor break points use out-of-date line numbers when a file is modified |
Date: | Mon, 4 Mar 2019 04:31:32 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 |
Follow-up Comment #8, bug #53702 (project octave): Just to confirm: I very rarely hit this issue of stale breakpoint locations and finding it impossible to set breakpoints on lines of code otherwise looking valid to me. I usually fix it by saving & reloading the file being debugged. I have the impression that esp. code lines immediately following comment lines are affected, but I can't put a finger on it. OTOH the situation is much better than it used to be > a year ago. (I'm currently using 6.0.0 and occasionally 5.1.1) _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?53702> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |