arm
Here are 1,862 public repositories matching this topic...
-
Updated
May 17, 2020 - C++
-
Updated
Jul 9, 2020 - C
There are a few flags that currently don't have proper error checking. The ones I found are -gc, -scheduler and -size. Using the wrong value will lead to no or unexpected errors.
I think the best way to handle it is to add a new method to compileopts.Config that checks whether there are any faulty flags, which is then called from the main function.
Is there a way to let the citra gdbstub automatically break on unmapped memory access? Right now, citra handles unmapped access gracefully and only spits out an error in the log. The real 3DS hardware will crash on unmapped memory access but the current Rosalina gdbstub will at least break with SIGSEGV and let you examine the process remains.
Would be nice if it was possible with citra as well ..
-
Updated
Jun 20, 2020 - Python
-
Updated
Jul 17, 2020 - C++
-
Updated
Jul 9, 2020 - C++
-
Updated
Jul 15, 2020 - C
Solutions
1. Convert INO files to CPP
2. Manual prototype declaration
#ifdef DO_NOT_USE
typedef int32_t delaytype;
void thisShouldNotAppearInTheBinary(delaytype timer); // aded manually
void thisShouldNotAppearInTheBinary(delaytype timer) {
delay(timer);
}
#endif-
Updated
May 16, 2020 - Python
-
Updated
Jul 2, 2020 - C
-
Updated
Jul 16, 2020 - Rust
-
Updated
Jul 17, 2020 - C#
-
Updated
Jun 8, 2020
-
Updated
May 29, 2020 - C++
-
Updated
Jul 15, 2020 - C++
-
Updated
Jul 17, 2020 - Shell
-
Updated
Jul 16, 2020 - OCaml
-
Updated
Nov 24, 2019 - Python
-
Updated
Jul 6, 2020 - Shell
-
Updated
Jul 9, 2020 - C++
-
Updated
Jul 1, 2020 - Shell
Improve this page
Add a description, image, and links to the arm topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the arm topic, visit your repo's landing page and select "manage topics."
Template name: 101-event-grid, https://github.com/Azure/azure-quickstart-templates/blob/master/101-event-grid/azuredeploy.json
The parameter eventGridSubscriptionUrl's description ends with:
This is no longer true, and deployments will fail, if the validation challenge is not answered, or the validation URL is not visited - even when