Strange information in Call Stack window while debugging

[rogeriodec_games]

Reproduction Steps

1) Put this on a script:

local function b()
	print('b')
end

local function a()
	coroutine.wrap(function()
		b()
	end)()
end

a()

2. Set a breakpoint on a() (line 11)
3. Run
4. Debug with step into (F11)
   

Expected Behavior

1) The call stack window should not show some lines like Line -1 [C]
2) When a function is called inside a coroutine, it should show the correct callback function a()

Actual Behavior

Opposite of above:

Issue Area: Studio
Issue Type: Other
Impact: High
Frequency: Constantly

[WheretIB]

@rogeriodec_games

1. The call stack window should not show some lines like Line -1 [C]

It shows all call frames that Luau VM has.
One of them is an anonymous C language closure that is used to resume coroutines.
Could be improved by displaying an explanation.

@rogeriodec_games

2. When a function is called inside a coroutine , it should show the correct callback function a()

I don’t get this, video shows

• function ‘b’
• unnamed function() that starts on line 6 (currently executes line 7)
• unnamed C coroutine resume function that can be improved or removed I guess
• function ‘a’
• unnamed script global function

[rogeriodec_games]

@WheretIB

One of them is an anonymous C language closure that is used to resume coroutines.
Could be improved by displaying an explanation.

So it’s not a bug, but a current feature, ok. If you could improve the display int this case, it will be appreciated.

@WheretIB

I don’t get this, video shows

• function ‘b’
• unnamed function() that starts on line 6 (currently executes line 7)
• unnamed C coroutine resume function that can be improved or removed I guess
• function ‘a’
• unnamed script global function

When b() is called at line 7 and the Step Into goes to line 2, Call Stack window should show the original function a() at Frame 1, but it’s currently showing nothing:

[music_man1996]

Just circling back here, this issue is fixed! Thanks again for the report.