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
Inevitably some third party will crash the underlying rust code in some fashion at which point it would be nice to have documented ways for extracting better debug output for those not familiar with rust and/or C.
For example, setting RUST_BACKTRACE=1 in the env and/or using gdb to run a python script using the python bindings to provide a backtrace (assuming debug symbols aren't stripped from the pkgcraft-c library).
The text was updated successfully, but these errors were encountered:
Inevitably some third party will crash the underlying rust code in some fashion at which point it would be nice to have documented ways for extracting better debug output for those not familiar with rust and/or C.
For example, setting RUST_BACKTRACE=1 in the env and/or using gdb to run a python script using the python bindings to provide a backtrace (assuming debug symbols aren't stripped from the pkgcraft-c library).
The text was updated successfully, but these errors were encountered: