#991
  • Created on
    2012-01-27 14:07
  • Reported by
    Vlad Dumitrescu
  • Status
    New
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    backlog
  • Plan Level
    -
  • Permission type
    Private
  • Estimate
    None/Small/Medium/Large Small
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

debugger: stepping behaves differently than in regular debugger

-module(f).

-export([f/0]).

Given the code below, with breakpoints on the first and last 'ok', executing "f:f()." stops at the first break. Choosing "step" twice does not stop at the second break. Choosing "run" does, as it should.

 f() ->
	ok,  % break
	g(),
	ok.

g() ->
	ok.  %break
User picture
  on 2012-01-27 14:48 *
By Vlad Dumitrescu
Priority changed from Highest (1) to High (2)
Priority changed from Highest (1) to High (2)
Lowering the prio a bit because this seems to never have been working. v0.9.0 has the same issue. Since nobody complained, probably nobody used it (or didn't notice it...) but it's kind of an embarrasing problem.
User picture
  on 2012-01-30 09:39 *
By Vlad Dumitrescu
Milestone changed from sprint #28 - 0.15 to sprint #29 - 0.16
Milestone changed from sprint #28 - 0.15 to sprint #29 - 0.16
Updating tickets (#937, #831, #972, #978, #957, #991, #967, #847, #858, #966, #917, #965, #964)
User picture
  on 2012-02-13 09:28 *
By Vlad Dumitrescu
Milestone changed from sprint #29 - 0.16 to backlog
Milestone changed from sprint #29 - 0.16 to backlog
Updating tickets (#859, #831, #972, #996, #995, #978, #957, #991, #847, #964, #917)
User picture
  on 2014-01-14 08:19 *
By Vlad Dumitrescu
Found in version changed from 0.14 to -none-
Priority changed from High (2) to Normal (3)
Found in version changed from 0.14 to -none-
Priority changed from High (2) to Normal (3)