Skip to content

Commit

Permalink
docs: Add set RUST_BACKTRACE=1 when using powershell on windows (#2035)
Browse files Browse the repository at this point in the history
* Update application.md

The provided command for setting RUST_BACKTRACE=1 on Windows was valid only if using cmd; while, if using PowerShell, that  command wouldn't work.

Added the powershell version too

* Update docs/guides/debugging/application.md

Co-authored-by: Fabian-Lars <[email protected]>

* fix powershell example code highlight

---------

Co-authored-by: Fabian-Lars <[email protected]>
  • Loading branch information
Giuliano1993 and FabianLars authored Apr 4, 2024
1 parent 288fd28 commit 573ec95
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion docs/guides/debugging/application.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,21 @@ Sometimes you may have an error in your Rust code, and the Rust compiler can giv
RUST_BACKTRACE=1 tauri dev
```

or like this on Windows:
or like this on Windows if you're using cmd.exe:

```shell
set RUST_BACKTRACE=1
tauri dev
```

or like this on Windows if you're using PowerShell:

```powershell
$env:RUST_BACKTRACE=1
tauri dev
```


This command gives you a granular stack trace. Generally speaking, the Rust compiler helps you by
giving you detailed information about the issue, such as:

Expand Down

0 comments on commit 573ec95

Please sign in to comment.