You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compilers may embed some debugging information directly into the compiled code or generate separate files (like .pdb for Windows or .dSYM for macOS) that contain debugging symbols and information. These files aid the debugger in correlating the machine code with the original source code.
If such method is possible, it will hugely benefit users using Rinf. Breakpoints will work if we run Rust code directly with cargo run, but will they work if they are linked to a Flutter app?
The text was updated successfully, but these errors were encountered:
@knopp I'm trying to get my workflow setup with flutter_rust_bridge and tested debugging. How ever I could not get this to work. I already wrote about it here.
As I wrote I'm using the gallery as an example. On one instance of vscode I started flutter debugger and on the other one I attached to this running process. Attach seems to work, but when I hit the breakpoint, the debugger only shows a message in Debug Console : Stop reason: signal SIGPROF and I can't debug anything.
Compilers may embed some debugging information directly into the compiled code or generate separate files (like .pdb for Windows or .dSYM for macOS) that contain debugging symbols and information. These files aid the debugger in correlating the machine code with the original source code.
If such method is possible, it will hugely benefit users using Rinf. Breakpoints will work if we run Rust code directly with
cargo run
, but will they work if they are linked to a Flutter app?The text was updated successfully, but these errors were encountered: