arm | Anonymizing Relay Monitor

While editing my initial question to add more context as Jay proposed I think it found the issue.

What probably happens? The view where the crash is, contains a table view. Each cell will be configured before being presented. I use a flag which holds the information, if the amount of weight for this cell (it is a strength workout app) has been initially set or is a change. When prepareForReuse is being called, this flag has not been reset. And that now means scrolling through the table view triggers a DB write for each reused cell, that leads to unnecessary writes to the db. Unnecessary, because the exact same number is already saved in the db.

My speculation: Scrolling fast could maybe lead to a race condition (I have read something about that issue with realm) and that maybe causes this weird crash, because there are multiple single writes initiated in a short time.

Solution: I now reset the flag on prepareForReuse to its initial value to prevent this misbehaviour.

The crash only happens when the cell is set up and the described behaviour happens. Therefor I'm quite confident I fixed the issue finally. Let's see. -- I was not able to reproduce the issue, but it also only happens pretty rare.

I'm having exactly that issue with my M1 Mac Mini.

Andronix allows you to run Linux and and Linux executables in an environment separate to the native one - but if you want to run a linux executable on an android, you can do so with much simpler tools, like adb. For example, adb shell ./sdcard/my_app.pe would theoretically work.

However, APKs in android are basically zip files that include metadata, and the compiled code as a dex file. You would typically use a platform like Android Studio to generate them from java code.

If you really want to implement things from scratch you probably need to compile your application into a jar file, and then convert it to the dex file using a tool like d2j.

There are two options I know of.

First, you can have buildx run builds on multiple nodes, one for each platform, rather than using qemu. For that, you would use docker buildx create --append to add the additional nodes to the builder instance. The downside of this is you'll need the nodes accessible from the node running docker buildx which likely doesn't apply to ephemeral cloud build environments.

The second option is to use the experimental docker manifest command. Each builder would push a separate tag. And at the end of all those, you would use docker manifest create to build a manifest list and docker manifest push to push that to a registry. Since this is an experimental feature, you'll want to export DOCKER_CLI_EXPERIMENTAL=enabled to see it in the command line. (You can also modify ~/.docker/config.json to have an "experimental": "enabled" entry.)

Your gadget is at 0x55555558f8.

Ropper shows the addresses of gadgets the way the ELF header describes the memory layout of the binary. According to that header:

• The file contents 0x0-0xadc are to be mapped as r-x at address 0x0.
• The file contents 0xdb8-0x1048 are to be mapped as rw- at address 0x10db8.

Account for page boundaries and you get one page mapping file offset 0x0 to address 0x0 as executable and two pages mapping file offset 0x0 to address 0x10000 as writeable.

From your GDB dump, these mappings are created at 0x5555555000 and 0x5555565000 in the live process, respectively.

Using answer of @Charles Duffy you can make older versions run on M1s. However Python versions before 3.8 will NOT be officially supported on M1 because they were not in bug-fix phase when M1 chips were released. It is stated clearly here as:

">Are there plans to backport PR 22855 to any branches older than 3.9?

The plan is to also support 3.8 on Big Sur and Apple Silicon as 3.8 is still in bugfix mode. There are no plans to backport support to 3.7 and 3.6 which are in the security-fix-only phase of their release cycles."

in this python bug tracker.

So I don't think there is any way to get them working on M1 unless someone tweaks python on their own.

Parents of 2b90506a8186 (both are good): […] I need to do second bisect to find actual first non-merge bad commit

You know merging 2b90506^2 produces a kernel that won't boot on your rig, so that commit has the bug that will show up in integration: it's bad.

You have a "mode": "Incremental" property on a resource 'subnetname1'. subnet does not take a mode parameter - see the reference: https://docs.microsoft.com/en-us/azure/templates/microsoft.network/virtualnetworks/subnets?tabs=json

However, when deploying virtual network, be aware of an well known problem - you need to specify subnets as a property of a vnet. Although you have option do deploy a subnet resource, when you run your template for the second time, virtualNetwork resource will try to remove all subnets (because property subnets is empty) - see more here: https://github.com/Azure/azure-quickstart-templates/issues/2786

Intel 32 bit is not executable on macOS since Catalina. Every Mac since 2006, except the original Intel Mac mini with Core Solo processor, is 64 bit capable.

Intel: clang -o myTool-x86_64 -mmacosx-version-min=10.15 -arch x86_64 main.c

ARM64: clang -o myTool-arm64 -mmacosx-version-min=10.15 -arch arm64 main.c

FAT binary: lipo myTool-x86_64 myTool-arm64 -create -output myTool