bernhardu

There are still issues, mostly with nested* tests. I tried to solve them for me, see the patches in #2890. I put there also a patch to default to ASan...

Hello, while trying to run on a specific host I looked a little through the buildkite config. Is there more to it to add this properly, or would something like...

As far as I see 'install.conf' is just available after the first installation attempt. Therefore the proposal by lope worked for me: /data/data/info.guardianproject.lildebi/app_bin/create-debian-setup.sh ``` --- create-debian-setup.sh.orig 2016-09-10 13:30:15.952076316 +0200 +++...

@lope. No, it is nothing comittable. Just wanted to be a little more verbose on the workaround for first installs.

@Jcfunk: user jonassmedegaard asked for a local proxy (approx) Either we have just small connections _or_ want to relieve the pressure on the mirrors ... ;-)

I tried to take a closer look to the debian bug and the stack canary gets overwritten here: https://github.com/resurrecting-open-source-projects/outguess/blob/24810e14327c2bbeedeaadd3e24491f2a4425c02/src/outguess.c#L164-L167 The destination of the memmove is always at least detect +...

There are new findings in the Debian bug report which lead to the crash happens when an error message should be printed. ```cpp Program received signal SIGSEGV, Segmentation fault. __strlen_avx2...

I mixed up the flags when I tried to create a rr test. This version shows a similar assertion as Wine: [mmap_private_from_fd_via_socket.c.txt](https://github.com/user-attachments/files/20533692/mmap_private_from_fd_via_socket.c.txt)

Thanks for the hints. Unfortunately all my tests to get into the MmappedFileMonitor path did still show a register diversion up to now.

In this case, would it be something to give a warning about this private mapping which may cause issues? Can this situation safe enough detected? So this is then maybe...