| 30 Jun 2021 |
Finn Behrens | I did destroy my build, while trying to enable spice-gtk. will finish that first. | 12:47:17 |
Finn Behrens | Sadly meson somewhere introduces -Werror, and I can't find where | 12:47:36 |
toonn | LnL: Hmm, I came up with a fix for cups, revealing another problem but I get a different hash even pre-fix. That's weird, no? | 13:41:52 |
Mic92 | kloenk: NIX_CFLAGS_COMPILE = [ "-Wno-error" ]; usually works against that. | 13:42:15 |
Finn Behrens | In reply to @joerg:bethselamin.de kloenk: NIX_CFLAGS_COMPILE = [ "-Wno-error" ]; usually works against that. Oh, ok. I found the line in meson.build and patched it. So it compiles now | 13:43:19 |
Finn Behrens | btw, I also compiled the x86 version and that does not segfault | 13:43:30 |
Finn Behrens | In reply to @joerg:bethselamin.de should still work with address sanitizer: https://stackoverflow.com/questions/55692357/address-sanitizer-on-a-python-extension I did this: DYLD_INSERT_LIBRARIES=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0/lib/darwin/libclang_rt.asan_osx_dynamic.dylib ./result/bin/virt-manager --no-fork --debug, but it does not look like a better backtrace for me | 13:52:51 |
Mic92 | kloenk: mhm. Maybe it is not an address violation than? | 14:16:04 |
Mic92 | Maybe it just calls abort | 14:16:09 |
Mic92 | GDB should be able to tell the difference | 14:16:21 |
Finn Behrens | or I'm unable to read the backtrace :-) | 14:16:41 |
Finn Behrens | In reply to @joerg:bethselamin.de GDB should be able to tell the difference yeah, not today :-) | 14:16:57 |
Mic92 | If you are unable to read the backtrace what is the backtrace than? | 14:17:33 |
Finn Behrens | It's not in the terminal window, but in a macos popup window | 14:18:13 |
Finn Behrens | Download python3.8_2021-06-30-155236_frodo.crash | 14:18:47 |
Mic92 | Finn Behrens: double free? | 15:14:00 |
Mic92 | Just a wild guess | 15:14:09 |
Mic92 | not sure what closure it was trying to free here: g_callable_info_free_closure | 15:14:50 |
Mic92 | Maybe a function it tried to call before in the same stacktrace? | 15:15:52 |
Mic92 | You might be able to get closure to the crash by adding random prints to the python code. Ideally those prints contain file and line number | 15:17:08 |
Finn Behrens | Hmm, yeah. I only did one code patch. So not exactly sure where to start. Also the same code patch works on x86 | 15:58:55 |
abathur | In reply to @domenkozar:matrix.org So if I understand the code correctly, it throws EOF error if there's no output from the builder Correct to read this as updating your understanding from i/o maybe helps with timing -> the fact of producing debug output prevents the error? | 17:08:12 |
| dotlambda joined the room. | 17:47:25 |
dotlambda | Redacted or Malformed Event | 17:47:58 |
| dotlambda left the room. | 17:56:17 |
| 1 Jul 2021 |
siraben | I'm getting untrusted substituters warnings after reinstalling Nix, how would I resolve that? | 02:47:55 |
Sandro | do you have nix-community as a substituter? | 05:21:27 |
siraben | warning: ignoring untrusted substituter 'https://gccemacs-darwin.cachix.org'
warning: ignoring untrusted substituter 'https://nix-remarkable.cachix.org'
warning: ignoring untrusted substituter 'https://hydra.iohk.io'
warning: ignoring untrusted substituter 'https://nix-community.cachix.org'
| 07:06:54 |
siraben | Sandro: fixed it by adding myself to trusted-users | 11:38:34 |
siraben | * Sandro: fixed it by adding myself to trusted-users in /etc/nix/nix.conf | 11:39:08 |