Panicing when running on my crate

[zxch3n]

I attempted to run the examples in my crate loro and encountered an issue.

warning: list was compiled with optimization - stepping may behave oddly; variables may not be available.
thread 'main' panicked at debugger/src/debugger.rs:386:21:
assertion failed: sb_frame.sp() <= active_frame.stack_pointer

The persistent warning, warning: list was compiled with optimization - stepping may behave oddly; variables may not be available, appears regardless of my configuration attempts. I am uncertain if this is the cause of the issue.

[zxch3n]

The program runs for a while after I remove all #[inline(always)]. Then:

thread 'main' panicked at debugger/src/debugger.rs:674:17:
assertion failed: sb_frame.sp() >= last_frame.stack_pointer

[tyt2y3]

Yes, you're right, inlining can be problematic. I'd suggest you to change your code to #[cfg_attr(not(debug_assertions), inline(always))]. That way you don't inline on debug build, and inline on production.

[zxch3n]

Understood. Is it possible to resolve this issue within the current project, or do we have other configuration options to circumvent the problem?

[tyt2y3]

Yes, I think so. On our side when parsing the source files, we can probably ignore #[inline] functions.