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
I spent an hour trying to reduce a minimal test case for this error I started experiencing with my app. I don't know if this is the right repo to track this, but so far I have produced the following:
When running this on any nightly compiler since nightly-2021-08-21, I get an error like this:
$ cargo +nightly-2021-08-21 run
Finished dev [unoptimized + debuginfo] target(s) in 0.03s
Running `target\debug\windows_explodey.exe`
error: process didn't exit successfully: `target\debug\windows_explodey.exe` (exit code: 101)
Adjusting the profile to panic = "abort" causes an even more ominous error:
$ cargo +nightly-2021-08-21 run --release
Finished release [optimized] target(s) in 0.03s
Running `target\release\windows_explodey.exe`
error: process didn't exit successfully: `target\release\windows_explodey.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)
I recognize it's probably silly to use #[windows_subsystem = "windows"] with env_logger. My workaround for now is conditionally calling env_logger::init() only on macOS and Linux.
The text was updated successfully, but these errors were encountered:
I spent an hour trying to reduce a minimal test case for this error I started experiencing with my app. I don't know if this is the right repo to track this, but so far I have produced the following:
When running this on any nightly compiler since
nightly-2021-08-21
, I get an error like this:Adjusting the profile to
panic = "abort"
causes an even more ominous error:I recognize it's probably silly to use
#[windows_subsystem = "windows"]
withenv_logger
. My workaround for now is conditionally callingenv_logger::init()
only on macOS and Linux.The text was updated successfully, but these errors were encountered: